interleaved status changes imply the wrong task was changed
Bug #426030 reported by
Martin Pool
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
If you look at for example https:/
It has two bug tasks, representing the fact that a fix is wanted in the stable series as well as in trunk. They can be independently targeted and prioritized. However, the interleaved status changes like
"Changed in bzr:
milestone: 2.0 → none "
imply that the status was changed in the trunk task, when some of them were being changed in other series.
I just untargeted the bzr/2.0 task and that didn't generate an entry at all.
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in launchpad: | |
| importance: | Medium → Low |
| tags: | added: confusing-ui |
To post a comment you must log in.
