-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The waiverdb UI prompt doesn't explain what the text box is for #2270
Comments
Is this issue open,@bowlofeggs? |
I believe that @ralphbean is fixing this in #2394. Is that correct Ralph? If so, can you update the commit message over there to also specify that it fixes this issue? Thanks! |
This should fix the UI in a couple places: - fixes fedora-infra#2363 - fixes fedora-infra#2270 There, it claims that only one failing result is waived, but a read through the method in `models.py` suggests that *all* unsatisfied requirements are currently waived. Signed-off-by: Ralph Bean <[email protected]>
Done. |
This should fix the UI in a couple places: - fixes fedora-infra#2363 - fixes fedora-infra#2270 There, it claims that only one failing result is waived, but a read through the method in `models.py` suggests that *all* unsatisfied requirements are currently waived. Signed-off-by: Ralph Bean <[email protected]>
This should fix the UI in a couple places: - fixes fedora-infra#2363 - fixes fedora-infra#2270 There, it claims that only one failing result is waived, but a read through the method in `models.py` suggests that *all* unsatisfied requirements are currently waived. Signed-off-by: Ralph Bean <[email protected]>
This should fix the UI in a couple places: - fixes fedora-infra#2363 - fixes fedora-infra#2270 There, it claims that only one failing result is waived, but a read through the method in `models.py` suggests that *all* unsatisfied requirements are currently waived. Signed-off-by: Ralph Bean <[email protected]>
This should fix the UI in a couple places: - fixes fedora-infra#2363 - fixes fedora-infra#2270 There, it claims that only one failing result is waived, but a read through the method in `models.py` suggests that *all* unsatisfied requirements are currently waived. Signed-off-by: Ralph Bean <[email protected]>
This feature is planned to be included in the upcoming 3.10.0 release: #2556. |
The fix for this issue has been deployed to Fedora's staging Bodhi instance: |
If a developer clicks on the waive button on an update, there is a pop up that has a text box and a submit button. The UI does not explain the purpose of this text box and it should. The text box is supposed to be justification for waiving the test failure.
The text was updated successfully, but these errors were encountered: