Status vs Resolution

Hi, Our Jira admin has created resolutions such as 'Ready to test', 'In test' and 'Deployed to production'.

I would have thought these should be statuses. Am I correct, or is he working within limitations of Jira?


4 answers

1 accepted

3 votes
Accepted answer

I would create them as statuses and assign them into a workflow. That way you can control how items transition between these states

They sound very much like status in a process to me, not resolutions. So I'm with Colin.

Thomas Schlegel Community Champion May 23, 2012


resolutions should be something like "fixed" or "won't fix" or some other things that describe, why an issue was closed. Usually, the solution does not change with every status change like "test" or "deployed".

Best regards


To me, “Resolution” should describe the state which resulted from the set of decisions that were made to bring the Jira issue to closure.

Resolution should not be conflated with Jira “Status”, which is a mechanism to describe a position in a workflow.

It depends on your organization structure if you use resolutions or statuses.

If you are a small group that does everything and do not need special permission to progress an issue through its lifecycle then resolutions will work. Assuming you resolve resolve first, then the resolution field takes you through the qa and deployment phases before you close.

If you have separate groups of people responsible for qa, deployment or special rules (manager approval for example) to progress an issue through its lifecycle then statuses are required becauses they are tied to transitions and transitions give you the place to validiate and approve the transition into the next status.

Another reason might be your workflow designer has not figured out yet how to a create a complete workflow and does not have the time to do that.

Thanks guys. So it's not a Jira limitation. I'll have to wait to point this out, I've been pointing out too much.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,725 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you