What state is used to determine "resolved" in the Created vs Resolved gadget?


I'm using the Created vs Resolved gadget for my project, and I'm not sure what state triggers "Resolved." Is it "Resolved" (which is an interim state for my project, like the developer has completed work), "Verified" (which is "Test team has confirmed the update and my desired terminal state), or "Closed" (Verified issues are changed to Closed when we release the product). 

I'm confident in Created looks at New state ;)

Thanks for any insight.


1 answer

It's driven by the "Resolution" field. 

If resolution = unresolved, then the issue is reported as open (i.e. not yet resolved).

If resolution is set to anything else, then the issue is seen as resolved.

Note that the "unresolved" JIRA shows you actually means "there is no value in the field". 

Some people make the mistake of adding options like "unresolved" to the list, which breaks, because the field is filled in, so the issue is resolved, whatever the option is named.

Ah yes. Thanks Nic. I'll have to remember to include a note about that in future answers about resolution-related stuff.

That resolution thing has to be one of the top three subjects of jive/osqa/answers/community since JIRA 2.0 was released!

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

905 views 3 9
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