It seems we have two different approaches, one old, one new.
The status and importance fields act in the old way, they take you to +editstatus
Clicking on the product name under affects will take you to the product. Yet the drop down takes you to +editstatus.
Clicking on the account under Assigned to will take you to the account. Yet the drop down takes you to +editstatus.
I believe the drop downs are correct. The action I would expect here is to click on them and edit the bug report.
I think we can improve the consistency by changing the Status link so that it links to https://help.launchpad.net/BugStatuses but leaving the drop down so it links to +editstatus. In this same vein, I propose we unlink the importance (e.g. high, medium) but keep the drop down link to +editstatus. These changes should make the display more consistent and folks (like me) can relearn the mappings without having to process exceptions. This would also specifically address Bug 185853 (which is a dup of Bug 29495). We could make this changes as part of Bug 29495.
It seems we have two different approaches, one old, one new.
The status and importance fields act in the old way, they take you to +editstatus
Clicking on the product name under affects will take you to the product. Yet the drop down takes you to +editstatus.
Clicking on the account under Assigned to will take you to the account. Yet the drop down takes you to +editstatus.
I believe the drop downs are correct. The action I would expect here is to click on them and edit the bug report.
I think we can improve the consistency by changing the Status link so that it links to https:/ /help.launchpad .net/BugStatuse s but leaving the drop down so it links to +editstatus. In this same vein, I propose we unlink the importance (e.g. high, medium) but keep the drop down link to +editstatus. These changes should make the display more consistent and folks (like me) can relearn the mappings without having to process exceptions. This would also specifically address Bug 185853 (which is a dup of Bug 29495). We could make this changes as part of Bug 29495.