bugs and tasks too confusing
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
When trying to discuss bazaar bugs, lifeless and I had a bit of confusion. Unable to close my own bugs, I gave lifeless a list of bugs that I had fixed so that he could make them closed. However, he hacked the url, which uses tasks.
Realizing the mistake, we then swapped sides. I gave him a list of tasks, while he was expecting a list of bugs.
Worse yet, bugs and tasks are usually *very* similiarly numbered, which means that if in conversation I say to lifeless "I fixed #164", he doesn't know whether I mean task 164 or bug 164.
I understand that tasks are going to be hidden, but they aren't yet, as if one edits the browser url, they're editing the task id, not the bug id.
From the user perspective, an easy way to fix this is to show b#bugnum / t#tasknum consistantly to the user. That way, if I tell somebody to look at "t3893", they'll know what I'm talking about.
| Changed in malone: | |
| status: | New → Rejected |
| Brad Bollenbach (bradb) wrote | #1 |
While your concerns about the confusion between bugs vs. task are 100% valid (to be honest, I hear people mixing them up all the time, along with the confusion about IDs, etc.) I don't feel that this is something that belongs in a bug report, because I don't think we're looking at one thing here that I can simply mark "Fixed." :)
It's a much deeper issue, and we haven't yet arrived at the One True Solution, despite a few attempts at it. When I last checked, our current plan of action was to leave it to mpt to improve the bug vs. task pages in such a way to clarify the distinction between the two, and hopefully stem the confusion.