Provide a workflow diagram of status changes in Malone

[Eleanor Berger]

~schmiedc suggested a tool that can really help users understand how Launchpad works - workflow diagrams which explain the changes a bug goes through during its lifecycle.

For an example, see http://www.bugzilla.org/docs/3.2/en/images/bzLifecycle.png

[Christoph Schmied (schmiedc)]

I think this is an great idea because (especially) new Users have all the different states of a bug on a single image and you can provide any information to those states which are necessary. Also you can include it on the wiki pages referring to it in a "better" way. The statechanges become much more clear.

For myself i wrote such diagrams in an summerjob with ms-viso ... helped me a lot that time to understand those changes.

[Eleanor Berger (intellectronica)]

This isn't really a duplicate of bug #29495. This bug is much more specific.

[Christoph Schmied (schmiedc)]

Well I would not say that is a duplicate entry. Of course both bugs point in
the same direction, namely to make it much clearer what each state is about.
But in the Bug Mathew Paul Thomas mentioned the goal is to discribe the
state where my suggestion was to build it up in a picture of the lifecycle.
So my goal was not to discuss about the states itself, but just get a
graphical view about the current way it is.

But of course we can get parts of those results into the sheet, we just have
to care about that it doesn't get wired again!

cheers

On Wed, Jan 21, 2009 at 11:44 AM, Matthew Paul Thomas <email address hidden>wrote:

> *** This bug is a duplicate of bug 29495 ***
> https://bugs.launchpad.net/bugs/29495
>
> ** This bug has been marked a duplicate of bug 29495
> Bug statuses should be better explained
>
> --
> Provide a workflow diagram of status changes in Malone
> https://bugs.launchpad.net/bugs/319322
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Launchpad Documentation: New
>
> Bug description:
> ~schmiedc suggested a tool that can really help users understand how
> Launchpad works - workflow diagrams which explain the changes a bug goes
> through during its lifecycle.
>
> For an example, see
> http://www.bugzilla.org/docs/3.2/en/images/bzLifecycle.png
>

[Christoph Schmied (schmiedc)]

So here is the first "prototype". Feel free to commit any suggestions! I really need your ideas what you think which information is missing :)

http://schmiedc.sc.funpic.de/data/bugs01.jpeg

cheers

[Christoph Schmied (schmiedc)]

Daniel Holbach told me that there are actually some sheets available at the ubuntu-wiki:
https://wiki.ubuntu.com/BugWorkflow?highlight=(CategoryBugSquad)

[Curtis Hovey (sinzui)]

A bug may skip "confirmed" and go directly to "triaged". The states are generally equivalent. Project owners may use triaged, all other users can only use "confirmed"

[Martin Albisetti (beuno)]

On Wed, Jan 21, 2009 at 11:28 AM, Curtis Hovey <email address hidden> wrote:
> A bug may skip "confirmed" and go directly to "triaged". The states are
> generally equivalent. Project owners may use triaged, all other users
> can only use "confirmed"

Until we make kiko's dream come true, and drop "confirmed" :)

--
Martin

[Christoph Schmied (schmiedc)]

So i have done a second one with a little bit more coloure and but the "Triaged" out of the happy path on the same high of confirmed. I hope i got the "Access Level" right.

http://schmiedc.sc.funpic.de/data/bugs02.jpeg

[era (era)]

You are lacking some valid paths which existed in the first sketch, e.g. from Incomplete back to New which I think is the normal case. Also from reading the docs linked to from other comments, I get the impression that Triaged should be understood as a step between Confirmed and In Progress, although it's optional in many projects.

If Won't Fix is used as a temporary condition, it should be possible to get back from Won't Fix to the state the bug was in before it got the Won't Fix status. Similarly for bugs which were not Invalid after all. https://wiki.ubuntu.com/BugWorkflow has a final chart which shows this in more detail, along with several other diagrams earlier in the page which essentially duplicate yours. Unfortunately, it's not clear whether that page is an early sketch for what eventually became the current system, or a plan for modifying the current system; in any event, it is also not 100% correct for the current process.

[Matthew Paul Thomas (mpt)]

era, where do you see that Won't Fix is a temporary condition? For all projects I've seen so far (including Launchpad itself), Won't Fix and Invalid serve exactly the same purpose.

[Christoph Schmied (schmiedc)]

well if i have untestood this both states right:
invalid means that this isn't a bug but Won't Fix says it is a bug but the
upstream (or whoever) istn't going to fix it.

But please correct me if im wrong!
cheers

On Mon, Jan 26, 2009 at 10:32 AM, Matthew Paul Thomas <email address hidden>wrote:

> era, where do you see that Won't Fix is a temporary condition? For all
> projects I've seen so far (including Launchpad itself), Won't Fix and
> Invalid serve exactly the same purpose.
>
> --
> Provide a workflow diagram of status changes in Malone
> https://bugs.launchpad.net/bugs/319322
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Launchpad Documentation: New
>
> Bug description:
> ~schmiedc suggested a tool that can really help users understand how
> Launchpad works - workflow diagrams which explain the changes a bug goes
> through during its lifecycle.
>
> For an example, see
> http://www.bugzilla.org/docs/3.2/en/images/bzLifecycle.png
>

[Matthew Paul Thomas (mpt)]

You are correct in theory. :-) In practice, however, developers often use "Won't Fix" as a polite way of saying "we're not going to change this" regardless of whether it's a bug or not. More importantly, there's no *functional* difference in Launchpad; bug reports go into (and occasionally out of) the Won't Fix state in just the same way as they go into (and occasionally out of) the Invalid state. You could show this in your diagram by clumping Won't Fix and Invalid together so that they have a single set of arrows going to/from them.

[Christoph Schmied (schmiedc)]

Ok thx .. will add the suggestions as i have time to and will come up with
the next chart :)

cheers

On Tue, Jan 27, 2009 at 11:43 AM, Matthew Paul Thomas <email address hidden>wrote:

> You are correct in theory. :-) In practice, however, developers often
> use "Won't Fix" as a polite way of saying "we're not going to change
> this" regardless of whether it's a bug or not. More importantly, there's
> no *functional* difference in Launchpad; bug reports go into (and
> occasionally out of) the Won't Fix state in just the same way as they go
> into (and occasionally out of) the Invalid state. You could show this in
> your diagram by clumping Won't Fix and Invalid together so that they
> have a single set of arrows going to/from them.
>
> --
> Provide a workflow diagram of status changes in Malone
> https://bugs.launchpad.net/bugs/319322
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Launchpad Documentation: New
>
> Bug description:
> ~schmiedc suggested a tool that can really help users understand how
> Launchpad works - workflow diagrams which explain the changes a bug goes
> through during its lifecycle.
>
> For an example, see
> http://www.bugzilla.org/docs/3.2/en/images/bzLifecycle.png
>