Dupes and tasks just confused me.
Bug #801 reported by
Christian Reis
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
I looked at
https:/
This bug is duped against bug 788, and has a new task on ubuntu dhcpd.
I then looked at
https:/
This bug has one task which is rejected.
Does this make sense? Is it not our fault? How could we have done better?
Revision history for this message
| Brad Bollenbach (bradb) wrote | #1 |
| Changed in malone: | |
| assignee: | bradb → nobody |
Revision history for this message
| Christian Reis (kiko) wrote | #2 |
| Changed in malone: | |
| status: | Confirmed → Invalid |
| description: | updated |
To post a comment you must log in.
For the purposes of simplicity of the initial implementation, not much thought has been given to how we'll deal with task merging/
But, I feel that you certainly raise an important point about this being currently non-obvious to interpret as a user. I plan to focus on a more complete dups implementation (talking to users, reaching some decisions on how to merge tasks, possibly even adding another kind of task status and/or "emergent bug property" for this kind of thing, etc.) after 1.0 is rolled out.
If you have some suggestions at the moment for how you would expect task merging/status changing to take place when a bug is marked dup, please feel free to document them here. Otherwise we'll glean more insight into this problem with some user discussion/