Information blueprints shouldn't need a priority
Bug #115158 reported by
Tim Penhey
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Informational specs often just end up with undefined priorities, and the concept of priority doesn't seem to fit well with informational specs.
| Changed in blueprint: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| tags: | added: confusing-ui |
To post a comment you must log in.
