Are there definitions for the various default statuses in workflows?

[Deleted user]

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.

[Nic Brough -Adaptavist-]

>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.

[Aniket Deshpande]

Whan Devs mark a bug as "Resolved", this means they have resolved/fixed the bug. And when the bug is marked as "Closed" usually by QA, it means they have verified the bug and yes it is fixed. Closed pretty much means the issue is closed.

[Nic Brough -Adaptavist-]

Sometimes, yes.  Often, people will do it differently.

[Deleted user]

Hi Nic, and thanks. You're comment, "generally "resolved" means "we think we've fixed it" and "closed" means "yes, you have" ", provided exactly the context which helped me distinguish the hierarchy involved in the two concepts.

[Logan Hawkes]

There is one more thing to consider. Jira's default behavior is to make issues read-only once they are closed. 

[Roger]

"resolved" means "we think we've fixed it" which is filled by the people who solved the problem.

"closed" means "yes, you have" which is filled by people who validates the ticket.

[Gaston Valente]

this can help:

https://confluence.atlassian.com/adminjiraserver071/working-with-workflows-802592661.html

this fragment is important:

Setting the resolution field

In JIRA, an issue is either open or closes, based on the value of its 'Resolution' field — not its 'Status' field.

• An issue is open if its resolution field has not been set.
• An issue is closed if its resolution field has a value (e.g. Fixed, Cannot Reproduce).

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:

• Set the resolution field automatically via a post function.
• Prompt the user to choose a resolution via a screen. See Working in text mode for details on this.

[Deleted user]

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.

[Niclas Sandstroem]

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