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

How to change the resolution back to unresolved?

I have a JIRA task that is marked as done but it should be unresolved. How do I change it?

5 answers

7 votes

Hi Natasha,

as Raynard already said, Jira offers you a built-in post function in workflows called "Update Issue Field" that enables you to update a few system fields. Selecting the field "Resolution" and selecting the value "None" results in the field value to be cleared. Depending on the workflow you're already using in that project, it can be that simply transitioning the issue to OPEN again, will clear the Resolution field.

Best, Max

So helpful! Thank you!!

5 votes

The resolution is changed in the post-function. If it needs to be unresolved, the next transition needs to have the post-function "Update Issue Field", select "Resolution", then select what you want that resolution to be.

Answers my query, thank you!

No answer here, this simply doesn't work to set the ticket back to an unresolved status.

My understanding of the Resolution field in Jira is that once any value is set for that field the ticket is considered closed and will show the strikethrough in reports and lists and those tickets will not be shown in the open ticket filter in the portal.

The problem I am seeing is that this post function doesn't set Resolution to NULL in the database. In my case it is setting it to the default value of Incomplete but again since there is a value in the Resolution field the system sees these tickets as closed.


If you think to do it using JIRA Automation, you can use this way.
A good tip: With this action RESOLUTION DATE will be clear together.resolution.JPG

Changed my reply into an Answer

Hi all,

I have tried all the different proposed solution for the automation, but nothing seemed to work for my situation.

I did find another approach which seemed to work in the end for me.

I created a new Resolution: "Re-opened" in Settings > Issues > Resolutions 

2023-01-03 11 17 57.png

And then I created a new Automation rule by going to Project Settings > Automation

Trigger: Issue Transitioned
From status: Done, Rejected, Duplicate

+ new component

New Action: Edit issue fields
Choose fields to set: Resolution
Value: Re-opened2023-01-03 11 22 55.png

Hope this helps who are in the same situation

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events