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 unresolved


i have tried to make resolution status resolved, but even though I have made postfunctions for transition to DONE, resolution still keeps showing as unresolved.

Which actually brings a lot of problems, because "reports" in that time shows, that there are no resolved issues, which is actually incorrect.

Any ideas?




Does your post function set the resolution to a value?  Have you published the workflow (if you were editing an active workflow, it goes into a draft mode, not changing the original until published)

Like Jason M_ likes this

I have published workflow, post function is set to resolved. Not sure what you mean by value?

Value is the content of the field (when it has one).

So you are saying your post-function is not working.  Could we see the configuration of it - both the summary in the workflow edit where all the post-functions are listed, and the content of the post-function (when you edit it from the summary)

Check one of the ticket histories for any updates to Resolution after moving ticket to closed status. Also check the transition post function for any errors after closing a ticket.

If there's no update for Resolution, either your workflow + post function was not published (as stated above), or perhaps you set the post function on the wrong transition. 

Also what post function are you using? I typically use the standard "Update Issue Field" method to set Resolution.

Hey, I have checked previous older requests and in history there is not even a mention about Resolution. Which brings me to my other question: if my workflow is incorrect how is it possible? Because I know for a fact, that the issue is in our DONE status, even though it is called somehow. What can be wrong in this case?


You have control over your workflow, if it is incorrect, it means one of your admins has introduced a problem into it (or neglected something if they created if from scratch)

Yeah, since I am the admin I will have to go through it all, but to be honest I do not have a clue, why it would not work.

I have added resolution to all steps (create, edit, view) and set automation, which is changing it for any request when it comes to certain fields. Which solved my issue.

Argh, NO, that's exactly the wrong thing to do.

You are now resolving all your issues as they are created or edited, so you've made a complete nonsense of all Jira's reporting on open and closed issues.

You should only put the resolution field on screens used in transitions that move an issue into a closed status.  You should have a post function to clear it on "re open" transitions.  

Snímek obrazovky 2022-06-23 123037.pngActualy I am not, because I have only put the resolution field in the screens and set this automation.

That automation is not fixing the duff data you are putting in, it's just doing what a post-function would do at certain times.

It doesn't repair the broken data you are putting in.

I don´t understand what you mean? What broken data? 

You said you are resolving issues as they are created.  That's broken data.

No, no, no I did not mean it this way. I am resolving issues as they are transitioned to any of DONE statuses.

You said "I have added resolution to all steps (create, edit, view) ", which reads as you entering a resolution when you create the issue.

Yes at the first time I have put it into create as well - i thought, that if it is not there, that it might be issue, but then I quickly realized, that reporter can choose the resolution and that is not what you want.

So I have stick it only to Edit and View - i still dont know though, what resolve screen does. But i have never used it, so i guess not much?


Log in or Sign up to comment
Community showcase
Published in Jira Software

Upcoming changes to epic fields in company-managed projects

👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...

14,988 views 37 49
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