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

Why doesn't the Resolution of a ticket doesn't change to Resolved when its Status is already Done?

My understanding was that Resolution in Jira would automatically update to Resolved or when a user is transitioning to Done they would need to select a Resolution value but this doesn't happen to our project. What could be wrong in our configuration?

1 answer

1 accepted

1 vote
Answer accepted

it is not automatically

I configured my workflow manually, so that on trasition "closed", it also sets the issue to "resolved".

And on "reopen" to "unresolved"

use post function:

or you can use addons like automation or scriptrunner, but post function should be the easiest.

The built-in post function is called simply "update field" and it's the same one for setting and clearing the resolution.  When it's saved though, it will show as "set the resolution to <xxx>" or "Clear the resolution" in the list of post-functions.  There's an example of the clear in the Jira system workflow (the one you can't delete)

Like John Funk likes this

Thank you for your answers. @Alexander Pappert and @Nic Brough _Adaptavist_ 

I've configured the post function. This means though that it won't be applied retroactively right? Is there any way I can edit the Resolution of the tickets I have that is already with the Done status?

Hello @Lena Boiser 

There are two ways that come to mind for how you can do this.

If your workflow allows it, transition the issue again from Done to Done (or whatever your closed status is). That will trigger updating the Resolution field. You can do that using the Bulk Change feature. Note, though, that might also update the Resolution Date field.

The second option is to add the Resolution field to your screens temporarily, and then use Bulk Change to update it, then remove it from the screens.

Hello Trudy,

Thanks for sharing. The first option I think would work but then the Resolution Date field wouldn't be accurate. The second option, I tried but the Resolution field doesn't show on the list of fields that can be updated when I do the bulk change. 

So yeah lesson learned from me definitely! 

I apologize for giving you bad advice. I recall it worked when I used that trick on JIRA Server a few years ago. I just tried it in JIRA Cloud, and I also see the field was not shown in Bulk Change / Edit Issues.

I did see, though, that the field was editable on individual issues in the Old Issue View. Depending on how many you have to update you might use that method to update them one at a time. You should check the first one you update, though, to see if changing that field affects the Resolution Date.

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

84 views 1 12
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