Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Automation to resolve issues does not mark as resolved

rfisher I'm New Here May 17, 2021

I have a very simple automation setup to transition an issue to resolved after 5 days of no response from customer. I choose resolved as the state to transition to and then choose done as the resolution field. This should resolve the issue, and it does set the status to resolved, but Jira still treats the issue as unresolved. Is there an additional step I am missing here?

3 answers


Can you share the log of the rule execution?


as initial view , it seems that you are trying to update resolution after closing the issue while this should be done during the transition in case you have applied properties on the Close status which doesn't allow any issue update 

Hello @rfisher 

Welcome to the community.

When you say that "Jira still treats the issue as unresolved", what exactly do you mean?

Are you working with a Company Managed project or a Team Managed project? Are you working with a Software, Service Management, or Work Management project?

0 votes
John Funk Community Leader May 17, 2021

Hi @rfisher  - Welcome to the Atlassian Community!

There are three things involved here - the status and the resolution field and the resolved field.

The status is usually something like Closed or Resolved or Done, and it is the last step in your workflow. It usually has a status category of Done (as opposed to In Progress or To Do).

The Resolved field is simply a date field that stores the date when the issue to move to a Done status category. 

Finally, the Resolution field captures information as to the type of Resolution. It can be something like Done or Obsolete or Won't Do, etc. There are many options out of the box for this. When this field is populated, that causes the issue to have the strike through.  

Can you share a screen shot that shows the status field and resolution field for the issue?

rfisher I'm New Here May 18, 2021

My automation is changing the status to resolved and setting the resolution to done but I haven't set the Resolved field. I will try that and see if it helps.



John Funk Community Leader May 19, 2021

The Resolved field gets set automatically by the system. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

244 views 7 7
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