headers
ilmcuts | 31 Dec 2008 13:42
Picon

Issue states in our bugtracker

Hi,

Happy New Year everyone!

Something in our bugtracker still makes my head spin. We have seven 
states for an issue:

New
Feedback
Acknowledged
Confirmed
Accepted
Resolved
Closed

Their intended use is documented here:
http://www.lsdev.org/doku.php?id=lsdev:bugs

If we can customize those states, can we whittle down the list?

If we can... We never really differentiate between "feedback" and 
"acknowledged". "Confirmed", and "accepted" are also very close in 
meaning. If you don't buy that... There's no clear divider between 
"acknowledged" and "confirmed", either.

My suggestion would be to condense those four to two.

And on a related note... I don't think we need both "trivial" and 
"tweak" for severity either. Pretty much everything is "minor" or 
"major" anyway, and if you do need to deviate from those you have
(Continue reading)

Permalink | Reply |
headers
chris | 21 Apr 2009 00:23
Picon
Favicon

Re: Issue states in our bugtracker

On 2008-12-31 04:42, ilmcuts wrote:
> And on a related note... I don't think we need both "trivial" and
> "tweak" for severity either. Pretty much everything is "minor" or
> "major" anyway, and if you do need to deviate from those you have
> "tweak" (even lower priority), "crash", and "block" (even higher priority).
>
> Anyone agree/disagree?

We haven't cleaned this part up yet... I suggest:

feature - self explanatory
minor   - most bugs (default)
major   - functionality is broken/not usable
block   - crash/ or must fix before next release

chris
Permalink | Reply |
headers
chris | 31 Dec 2008 21:12
Picon
Favicon

Re: Issue states in our bugtracker

ilmcuts <ilmcuts <at> ...> writes:
> If we can customize those states, can we whittle down the list?

We can, but it takes some work.

Here is the current list and use cases just for easier reference in this thread.

New: A newly submitted issue, no action has been taken.

Feedback: Further information is needed before we can confirm or start working
on the issue.

Acknowledged: We have not confirmed the issue yet, however it looks valid and
we'll look into it.

Confirmed: The issue has been confirmed, and it appears to be valid. At this
point no one is working on it.

Accepted: The issue is being worked on.

Resolved: The issue has been fixed and committed to the source repository.

Closed: If the issue was fixed, then the issue has been included in a release.
If the issue was not fixed, then it was invalid and simply closed.

The expected current work flows are these:

(normal bug flow)
New -> Acknowledged -> Confirmed -> Accepted -> Resolved -> Closed
(Continue reading)

Permalink | Reply |
headers
Tobbe Lundberg | 31 Dec 2008 14:49
Picon
Gravatar

Re: Issue states in our bugtracker

> Happy New Year everyone!

You too! :)

> Something in our bugtracker still makes my head spin.

> Anyone agree/disagree?

Yeah. It could definitely use some simplification!

//Tobbe
Permalink | Reply |
headers
ilmcuts | 10 Feb 2009 19:29
Picon

Re: Issue states in our bugtracker (UPDATED)

Hi all,

Just a little update on this, we have trimmed the list of issue states 
in the bugtracker. The new list can be found here:

http://www.lsdev.org/doku.php?id=lsdev:bugs

In short, there are only four states left:
Feedback, Confirmed, Resolved, Closed

The change has been in effect for a few weeks already, but I guess we 
never put out a note saying so.

-ilmcuts
Permalink | Reply |

Gmane