It's very difficult to discover how to mark a bug "Fixed"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Medium
|
Brad Bollenbach |
Bug Description
It's very difficult to discover how to mark a bug fixed when looking at the bug index page. It also takes a number of clicks to do so, even for those familiar with the process.
The current process, from the point where you arrive on the bug page, is as follows.
1. In the "fix requested for" column, click on the (non-underlined) name of the product or package where the bug has been fixed. (Usually this cell is orange.)
2. If the next page says "To change the information below, you must be logged in", do not click "Log In"! Instead click "change the information below", and log in on the next page.
3. From the "Status" menu, choose "Fixed". Then scroll down and click "Save Changes".
This process is in need of vast improvement. If not logged in, it requires four page loads; it should require only two. If logged in, it requires two page loads; it should require zero.
The bogosity of step 2 is covered by bug 2883.
Changed in malone: | |
assignee: | nobody → bradb |
status: | New → Accepted |
description: | updated |
summary: |
- Many users have asked the following question after clicking on a bug in - the bug listing: - - /How do I mark this bug fixed?/ - - It's very difficult to discover how to mark a bug fixed when looking at - the bug index page |
I can confirm it. Maybe until the web ui
is reworked, please add a short howto do
it now to this bug report.