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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,672
Community Members
 
Community Events
184
Community Groups

difference between issues resolved and issues closed

Edited

I need to count the number of resolved tasks. A task is considered closed (crossed out on the board) when it changes to the green closing status. From the documentation: Issues resolved are those that have a resolution date, and Issues closed are those that take into account the date the issue was finally closed (that is both, issues with resolution date and issues without a resolution date). Can you help me figure out why some closed tasks (which have moved to the closing status and are crossed out) indicate the resolution date, while others do not? How do they differ and what determines whether the tasks is resolved or closed?

2 answers

1 accepted

2 votes
Answer accepted
Jeroen Poismans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 10, 2023

Hi Natalie and welcome to the Atlassian Community!

As you mentioned these are indeed 2 different things. An issue can be in a "Done" status without being actually resolved.

It is good practice to provide a resolution when closing an issue. That way a resolution date is automatically set and the issue is considered resolved for Jira (and it gets crossed out). If no resolution is set, your issue might "seem" done, by being in a "Done" status, but actually it is not.

How can you fix this?

  • In the workflows, in the transition to "Done", show a transition screen with the required Resolution field to be filled out (by adding a validator)
  • In the workflow, in the transition to "Done", set the Resolution field with a resolution.

Hope this helps you!

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 10, 2023

Adding to this...

The Resolved date gets set when the Resolution field gets set. The Resolution field is separate from the Status field where you set the status of the issue to Done (or Closed or some other done/green status). And the Resolution is not necessarily automatically being set when an issue transitions to a green/done status.

You can see the three fields in the Advanced Issue Search screen.

Screen Shot 2023-05-10 at 3.51.47 PM.png

 

And here is an example where issue Status was set to Done but Resolution was not set. The italicized value Unresolved is used to indicate the Resolution field has no value. The field is not actually set to Unresolved. Notice that there is no Resolved date in these cases.

Screen Shot 2023-05-10 at 3.52.24 PM.png

Like Natalie likes this

Thanks a lot for your answers!

Thanks a lot for your answers!

Suggest an answer

Log in or Sign up to answer