Lack of definition within launchpad on bug status meanings
Bug #889088 reported by
Dan Harrop-Griffiths
This bug report is a duplicate of:
Bug #29495: Lack of definition within launchpad on bug status meanings.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
- The lack of definition within launchpad on bug status meanings is confusing - especially to new users. This can result in bug's being given a wrong or misleading status. This can also lead to different projects interpreting bug status meanings differently. It's hard to work out what's what without a common starting point.
URL - Multiple pages, general Launchpad issue.
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: ui |
To post a comment you must log in.
We discussed changing the (enum-)picker to show the definition of each item. For example
New
This bug and has not yet been reviewed and verified.
Confirmed
This bug has been reviewed, verified as something needing fixing.
Triaged
The bug report contains all information a developer needs to start work on a fix.
^ This example does not use the actual definition from bugs/interfaces /bugtask. py /help.launchpad .net/Bugs/ Statuses
lib/lp/
Which is an astonishing read. BugTaskStatus and BugTaskImportance do not match
https:/
and I honestly do not understand some of the terms. I think the definition in Lp's
code was written from an early Ubuntu perspective. We require the definitions to
be applicable to all projects that use Lp...those that are not can be considered for
removal.