This question is in reference to Atlassian Documentation: Defining status field values
I'm trying to find basic documentation on the Atlassian's meanings for various statues. How is Done different from Resolved, different from Closed, and in what order should they be used in a workflow? They must be important or they wouldn't exist, but I've just spent the past 20 minutes navigating in circles trying to find Atlassian's definitions of these.
this can help:
this fragment is important:
In JIRA, an issue is either open or closes, based on the value of its 'Resolution' field — not its 'Status' field.
This is true regardless of the current value of the issue's status field (Open, In Progress, etc). Therefore, if you need your workflow to force an issue to be open or closed, you will need to set the issue's resolution field during a transition. There are two ways to do this:
Thanks Gaston. Highlighting this specific section has helped clarify for me the concept that in Jira Statuses and Resolution. It seems like status round-robin with issue participants lobbing status values back and forth, while Resolution is simply a binary state of Open or Closed.
In all the time I spent reading Atlassian documentation the delineation of the relationship between these two was never clearly addressed even though it is a critical relationship.
>How is Done different from Resolved, different from Closed,
They tend to be used by different workflows. Done is more of an Agile thing that really does mean "this issue needs no more work". Resolved and Closed are from a slightly more traditional JIRA workflow - have a look at the built-in system workflow to see how they're used, but generally "resolved" means "we think we've fixed it" and "closed" means "yes, you have"
>in what order should they be used in a workflow
Whatever order makes sense to your process.
This is a bit freely upon how you want to slice the cake. Basically you have backlog/new, being worked at/in progress and done/closed/resolved as statuses. Blue, Yellow, Green categories
No matter status an issue is not treated as closed without a resolution.
Screen Shot 2017-03-07 at 20.43.38.pngScreen Shot 2017-03-07 at 20.44.04.png
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events