What is the difference between a Resolution and a Status that is of category Done?

[Stuart Mills]

Hi All,

I'm getting a little confused when organizing all of my workflows.

What it Atlassian's definitive stance on when all actions on an Issue are finished?

Does a status of the category "Done" mean that the issue is for all intensive purposes no longer expected to be worked upon?

Or is it only when a Resolution is Set is the issue finished?

I'm a little confused on what I should have all of my workflows 'end' up as.  Where do I want them to be?

Should all of my completely finished issues end up with;

1. Status: Resolved (category Done)

2. Resolution: Set

and/or any other properties?

[Bastian Stehmann · Accepted solution]

Hi @Stuart Mills ,

Jira  handles all issues without a set resolution as open and with a resolution set as resolved.

There are many things that rely on this, for example the my open issues filter/gadget.

For this it doesn't matter, if the status is done or something else.

So you should make sure, that the resolution is set in the last status of your workflow (and removed when you reopen an issue). You can call it whatever you like.

To be consistent, the status that you are you using for the done status, should be of the done status category. 

[Stuart Mills]

Thank you Bastian for your response - this makes sense to me, very simply laid out.

The impactful statement for me was: "make sure, that the resolution is set in the last status of your workflow (and removed when you reopen an issue)."

[Deleted user]

Hi @Stuart Mills ,

Basically the Jira workflow is a set of statuses and transitions that an issue moves through during its lifecycle. An issue's status indicates its current place in the project's workflow. 

Resolutions are the ways in which an issue can be closed, or completed, or resolved, in many ways. An issue resolution is usually set when the status is changed.

There is some good documentation about the status and resolution fields.

https://confluence.atlassian.com/cloudkb/best-practices-on-using-the-resolution-field-968660796.html

https://confluence.atlassian.com/adminjiracloud/working-with-workflows-776636540.html

https://confluence.atlassian.com/adminjiracloud/issue-statuses-priorities-and-resolutions-973500867.html

https://confluence.atlassian.com/adminjiracloud/configuring-statuses-resolutions-and-priorities-776636333.html

Regards,
Kishore 

[Stuart Mills]

Thanks Kishore,

Appreciate the links to extra reading.  I'm working through them now.  Definitely expanded on what Bastian said.

I'm glad I came across an Atlassian source document, that states "Don't create a Resolution named "Unresolved"/"None"" and the risks of doing so - great info and I actually asked myself during my workflow design why I couldn't do this.

Thank you!