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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Resolution field behavior - adding new and retroactive updates

We were originally only using the "status" field in JIRA to track when something is closed. We have since discovered the value of the "resolution" field in JIRA and are now hoping to add this function back for two of our projects. However, I've run into a few questions. 

1) If I update the workflow by adding a post function, do I need to update anything else in the settings (i.e. screens, schemes, etc) or will the workflow suffice?

2) This might be answered in the previous question, but if I have multiple resolution options (done, won't fix, etc), where will the user be able to select this field? I'm guessing it is probably related to a transition screen/scheme, but figured I would check. 

3) We are hoping to tie our resolution of Done with our status of Closed. By introducing the post function into our workflow, will all of the previous JIRA tickets get automatically updated with the resolution, or will I need to perform a mass update?

Thanks in advance to anyone who can help!

3 answers

2 accepted

2 votes
Answer accepted
John Funk Community Leader Apr 17, 2019

Hi Yvonne,

Agree with Ismael for number 1 above - it should definitely work.

For number 2, we actually have different statuses (and therefore transitions) for different types of resolutions. We use Discard for issues that are dropped and never started. We use Aborted for issues that were started but we are not going to finish. That way we can keep metrics on those. 

So for Discard and Aborted, we set the Resolution to Obsolete. And with the Closed (Done) transition, it is simply set to Done. 

You will definitely need to do a bulk edit for number 3. 

I hope that helps!

1 vote
Answer accepted
Ismael Jimoh Community Leader Apr 16, 2019

Hi @Yvonne Henderson 

1. Updating the workflow post function will suffice if only one resolution would be set every time. If not add a screen to the transition that contains the resolution field.

2. Answered in 1

3. Previous tickets need to be updated using bulk edit function. Jira doesn’t automatically change it.

Hope this helps.

Hi ! Could you also tell us how to update all tickets (third point). When you choose the option bulk edit, I see the possibility to edit the transitions, but I don't find a "general update" functionality. 

Kind regards,

John Funk Community Leader Jun 17, 2020

You have to add a new transition that loops itself from Done to Done. Then you put a post function on the new transition to set the Resolution to Done. Then you can do a bulk change and transition all of the issues with the new looping transition. 

@Yvonne Henderson 

1) Post function will do the job

2) Transition and therefore the post function is associated with a particular status unless you reuse the transition. Never had discrepancies with this

3) Unfortunately no, however, you can try our free addon (Quantify) that has a special tool for this. Because we provide insights for Kanban boards like throughput (rate of resolved ticket per unit of time) we have the data to fix this.

@George Mihailoff 

We had the Quantify app.  How does it allow updating of the resolution field?  I have tried to find it in the online Quantify documentation and there isn't anything there about how the app does this?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events