For non-LP upstream, bug watch should be mutually exclusive with assignee
Bug #111946 reported by
Matthew Paul Thomas
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Low
|
Unassigned | ||
Bug Description
When a bug report is open on an upstream project that does not use Launchpad for bugtracking, but is not yet linked to a report in that project's bugtracker, the "Affects" form suggests that you can enter both an assignee *and* a bug watch. This isn't true: if the bug is linked to a bug watch, what you enter in the assignee form will be ignored.
More logical would be something like this.
Bug status is tracked:
(*) Manually
Status: [Unconfirmed :^]
Importance: [Undecided :^]
Assigned to: (*) Nobody
( ) Me
( ) [______________]
( ) In a remote bugtracker
URL: [______
| Changed in malone: | |
| status: | Unconfirmed → Confirmed |
| Changed in malone: | |
| status: | Confirmed → Triaged |
| importance: | Undecided → Low |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
| Changed in launchpad: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
We don't use complex forms now, so the analysis here doesn't directly speak to the problem. Beyond that, remote bugs can in principle have an assignee (inferred from the remote tracker) - so the real issue is something like 'for a bug watch, we should show but not permit editing task fields' - and I believe that that is the case today.