Cannot target a task to a series if another task already targetted
Bug #162411 reported by
William Grant
This bug report is a duplicate of:
Bug #110195: Nominating a bug for a distro series affects all package tasks for that distro.
Edit
Remove
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Critical
|
Unassigned | ||
Bug Description
If a bug has multiple Ubuntu package tasks, and one is targetted to a series, the checkbox to nominate to that series is no longer present. That is wrong, as I do actually want a Dapper task on the other package. This should only currently happen with fairly old bugs (targetted before the new release management stuff landed), but hopefully that will be untrue once bug #110195 is fixed.
A workaround for this is probably to add the task using the email interface, but that does things wrong, and is a bug too (no permissions, incorrect sorting, general death and destruction).
Revision history for this message
| William Grant (wgrant) wrote Workaround now crashes | #1 |
Revision history for this message
| William Grant (wgrant) wrote Re: Cannot target a task to a release if another task already targetted | #2 |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: oops |
| Changed in launchpad: | |
| importance: | Low → Critical |
| summary: |
- Cannot target a task to a release if another task already targetted + Cannot target a task to a series if another task already targetted |
| description: | updated |
To post a comment you must log in.
One can no longer work around this using the email interface. One gets OOPSes like OOPS-816CEMAIL2.