| 2005-06-09 18:52:31 |
Brad Bollenbach |
bug |
|
|
added bug |
| 2005-11-02 20:20:12 |
Brad Bollenbach |
malone: status |
New |
Accepted |
|
| 2005-11-02 20:20:12 |
Brad Bollenbach |
malone: assignee |
|
bradb |
|
| 2005-11-15 21:45:31 |
Matthew Paul Thomas |
description |
Often times, users ask us what the task status "Accepted" means. Does it mean that the bug's been confirmed as really being a bug? Does it mean that somebody's working on the bug? Or does it mean something entirely different?
I recommend that it may make sense to rename "New" and "Accepted" to "Unconfirmed" and "Confirmed", respectively, to be clear that these are really the two states that border the verification by someone with enough experience to say this is indeed a bug. |
Often times, users ask us what the task status "Accepted" means. Does it mean that the bug's been confirmed as really being a bug? Does it mean that somebody's working on the bug? Or does it mean something entirely different?
It may make sense to rename "New" and "Accepted" to "Unconfirmed" and "Confirmed", respectively, to be clear that these are really the two states that border the verification by someone with enough experience to say this is indeed a bug.
This distinction is mutually exclusive with the distinction that would be made by fixing bug 1346, unless we get "Unconfirmed", "Confirmed", and "Accepted" states. |
|
| 2005-11-15 23:15:14 |
Matthew Paul Thomas |
description |
Often times, users ask us what the task status "Accepted" means. Does it mean that the bug's been confirmed as really being a bug? Does it mean that somebody's working on the bug? Or does it mean something entirely different?
It may make sense to rename "New" and "Accepted" to "Unconfirmed" and "Confirmed", respectively, to be clear that these are really the two states that border the verification by someone with enough experience to say this is indeed a bug.
This distinction is mutually exclusive with the distinction that would be made by fixing bug 1346, unless we get "Unconfirmed", "Confirmed", and "Accepted" states. |
Often times, users ask us what the task status "Accepted" means. Does it mean that the bug's been confirmed as really being a bug? Does it mean that somebody's working on the bug? Or does it mean something entirely different?
bradb and mpt have concluded that Malone should have states "Unconfirmed", "Confirmed", and "Being fixed". In line with bug 1346, only the assignee should be able to set the state to "Being Fixed"; that way people can see and understand whether someone is working on a bug or not. |
|
| 2005-12-01 20:01:21 |
Matthew Paul Thomas |
summary |
Often times, users ask us what the task status "Accepted" means |
|
|
| 2005-12-01 20:01:21 |
Matthew Paul Thomas |
description |
Often times, users ask us what the task status "Accepted" means. Does it mean that the bug's been confirmed as really being a bug? Does it mean that somebody's working on the bug? Or does it mean something entirely different?
bradb and mpt have concluded that Malone should have states "Unconfirmed", "Confirmed", and "Being fixed". In line with bug 1346, only the assignee should be able to set the state to "Being Fixed"; that way people can see and understand whether someone is working on a bug or not. |
Often times, users ask us what the task status "Accepted" means. Does it mean that the bug's been confirmed as really being a bug? Does it mean that somebody's working on the bug? Or does it mean something entirely different?
To resolve this confusion and encourage better Malone workflow, bradb, mpt, and kiko have concluded that Malone should have these states:
"Unconfirmed" (renamed from "New")
"Needs Info" (renamed from "NeedInfo")
"Rejected" (no change)
"Confirmed" (renamed from "Accepted")
"In Progress" (new state)
"Fixed" (renamed from "PendingUpload")
"Released" (renamed from "Fixed").
In line with bug 1346, only the assignee should be able to set the state to "In Progress"; that way people can see and understand whether someone is working on a bug or not. |
|
| 2005-12-01 20:01:21 |
Matthew Paul Thomas |
title |
New/Accepted task statuses might be better named Unconfirmed/Confirmed |
Rename New/Accepted statuses as Unconfirmed/Confirmed, and other tweaks |
|
| 2005-12-09 15:39:04 |
Brad Bollenbach |
malone: status |
Accepted |
NeedInfo |
|
| 2005-12-14 16:33:52 |
Brad Bollenbach |
description |
Often times, users ask us what the task status "Accepted" means. Does it mean that the bug's been confirmed as really being a bug? Does it mean that somebody's working on the bug? Or does it mean something entirely different?
To resolve this confusion and encourage better Malone workflow, bradb, mpt, and kiko have concluded that Malone should have these states:
"Unconfirmed" (renamed from "New")
"Needs Info" (renamed from "NeedInfo")
"Rejected" (no change)
"Confirmed" (renamed from "Accepted")
"In Progress" (new state)
"Fixed" (renamed from "PendingUpload")
"Released" (renamed from "Fixed").
In line with bug 1346, only the assignee should be able to set the state to "In Progress"; that way people can see and understand whether someone is working on a bug or not. |
Often times, users ask us what the task status "Accepted" means. Does it mean that the bug's been confirmed as really being a bug? Does it mean that somebody's working on the bug? Or does it mean something entirely different?
To resolve this confusion and encourage better Malone workflow, bradb, mpt, and kiko have concluded that Malone should have these states:
"Unconfirmed" (renamed from "New")
"Needs Info" (renamed from "NeedInfo")
"Rejected" (no change)
"Confirmed" (renamed from "Accepted")
"In Progress" (new state)
"Fixed" (renamed from "PendingUpload")
"Released" (renamed from "Fixed").
As per a discussion between SteveA and kiko, we may need to do more thinking about the appropriateness of the names "Fixed" and "Released", but will postpone this thinking until after the first cut has landed.
In line with bug 1346, only the assignee should be able to set the state to "In Progress"; that way people can see and understand whether someone is working on a bug or not. |
|
| 2005-12-14 16:34:11 |
Brad Bollenbach |
malone: status |
NeedInfo |
Accepted |
|
| 2006-01-09 15:25:45 |
Brad Bollenbach |
malone: status |
Confirmed |
Fix Released |
|
