Merge lp:~wallyworld/launchpad/filebug-choice-widgets-1003748 into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Curtis Hovey |
Approved revision: | no longer in the source branch. |
Merged at revision: | 15325 |
Proposed branch: | lp:~wallyworld/launchpad/filebug-choice-widgets-1003748 |
Merge into: | lp:launchpad |
Diff against target: |
355 lines (+207/-8) 8 files modified
lib/lp/app/browser/lazrjs.py (+4/-2) lib/lp/app/javascript/choice.js (+39/-0) lib/lp/app/widgets/tests/test_itemswidgets.py (+9/-0) lib/lp/bugs/browser/bugtarget.py (+18/-0) lib/lp/bugs/browser/tests/test_bugtarget_filebug.py (+54/-1) lib/lp/bugs/javascript/filebug.js (+10/-2) lib/lp/bugs/javascript/tests/test_filebug.html (+16/-0) lib/lp/bugs/javascript/tests/test_filebug.js (+57/-3) |
To merge this branch: | bzr merge lp:~wallyworld/launchpad/filebug-choice-widgets-1003748 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Curtis Hovey (community) | code | Approve | |
Review via email: mp+107616@code.launchpad.net |
Commit message
Add progressive enhancement for status and importance popups on file bug page.
Description of the change
== Implementation ==
The branch provides functionality to enhance the +filebug form when javascript is enabled. The standard form uses simple drop down combo controls for bug status and importance. These controls are replaced with choice source popups the same as used on the bugtask form itself. So the user gets nice colours and descriptions etc.
The way it works is that the drop down combo is hidden and the choice source popup is rendered in its place. The the popup choice is made, it is saved to the hidden combo widget so that when the form is saved, the correct value is passed to the back end.
I have made an addition change for the popups. Not all of the available bug status choices are valid when filing a bug. Specifically, these choices have been excluded from selection:
- expired
- invalid
- opinion
- won't fix
- incomplete
So the user gets to choose from:
- new
- confirmed
- triaged
- in progress
- fix committed
- fix released
The latter 2 choices allow a bug to be file retrospectively for a fix that has already been completed.
== Tests ==
Add new yui tests for the additional file bug functionality.
Update the TestFileBugRequ
Update TestVocabularyT
= Lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/
lib/lp/
lib/lp/
lib/lp/
lib/lp/
lib/lp/
lib/lp/
Wow. Thank you.
I do not think "Confirmed" should be in the list given your reasoning. Confirmed means someone other than the bug reporter is affected by the bug, so the UI should not let me cheat. If I am the triager, I can set "Triaged" to mean someone affiliated with the project acknowledges the bug.