Why do many Jira Workflows not set Resolution while Jira Assumes this field Defines Open/Done?

Many queries, like the system "My Open Isuses", assumes that the Resolution = Unresolved is the key to seeing if an issue is completed or not.

Jira now has some very handy Project Templates and Workflows that offer many out of the box solutions. The problem I am seeing is how many just do not set a resolution? Even the "Typical Software Development" workflow does not set the resolution.

This makes queries that rely on the resolution field useless. In this case I have no way to remove the "Done" Issues from my "Open Isuses" Filter.

So while I know that I can fix this in the workflow...why is the system and the "common" workflows not matching up? Just adding 'AND status != Done' would actually make a lot of these workflows work without needing extra modifications.

4 answers

What's the version of your JIRA?

We are currently on v6.1.1.

Just adding 'AND status != Done' is not the way to go. Actually a workflow post function should be created so that JIRA will automatically set the issue Resolution.

I think Atlassian might need to look at this as a future improvement.

Yes I agree...a post function (for Done) would be ideal.

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,911 views 19 22
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