Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Seeking definition of Jira's "Created vs. Resolved Issues Report"

Will someone kindly point me to a source that describes the algorithm for what designates a Defect as "resolved"? 


Is this the only information that is published? 

Setting the Resolution field

In JIRA, an issue is either Open or Closed, 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. FixedCannot Reproduce).

This is true regardless of the current value of the issue's Status field (OpenIn Progressetc).

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.

1 answer

1 accepted

0 votes
Answer accepted

Yes this is accurate. You need to have the resolution field set in order for the report to work. 
this is one way to do it. Another is to use a transition screen

You would use a post function as you outlined if the resolution should always be set to the same thing(done, duplicate , won’t fix etc) 

you should use the transition screen if you want to limit the number of done statuses or you want to have people select the why an issue is resolved. This allows for more granular reporting if it’s something your users desire while also limiting how many statuses are needed in your jira

resolution is a very important field that is often not set. I would recommend running the following jql on your jira instance and it will determine which workflows need to be updated 

statusCategory=Done AND resolution is EMPTY

you can then fix the resolutions by bulk changes or if you have script runner they have a built in script for this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

876 views 14 20
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you