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

Update resolution date with Automation rules


I recently created a field call "resolution date" for my projects and I would like for this date to be updated when I change the status to some other status (done, close, rejected, ...).

I am trying to do that by created an Automation rules but I have difficulties to do it. Could someone help me ? 

Here is a picture of what I've done so far automation rules.PNG

3 answers

3 accepted

1 vote
Answer accepted
John Funk Community Leader Jun 21, 2021

Hi @C. SIMON  - You cannot control the value of the Resolved field. That is controlled by the system and is populated when the issue is marked resolved (i.e. a value is placed in the Resolution field). 

So, I think you might be asking if you can mark it resolved earlier than the date that is getting set, and the answer is no. You could mark it later by simply updating the Resolution field to a new value, and it would capture the date at that time. But you cannot make it earlier. 

John Funk Community Leader Jun 26, 2021

Hey @C. SIMON  - Any feedback?

Hello, I find the way to activate resolution field on our issue. It's perfectly working. Now I just have to correct all the issues =

- a status = done and

- resolution = unresolved and

- resolution date = empty

How can i do in bulk change ?  I would like that resolution date = update date ?

Thank you for your help.


0 votes
Answer accepted
Daniel Ebers Community Leader Jun 26, 2021


if I understand you correctly you have created a new custom field "resolution date" which is separate from the system field, is this correct?

For the system field John and Fazila already stated important information to consider, there are technical limitations like they said.

On the other hand, could you please describe the use case for a custom field for "resolution date" - it would Community members more likely allow to make a proposal.

Is this a company-managed or team-managed project? Also you said you are struggeling with the rule of some kind - is it not working or giving back wrong results?

Could you probably also post an log of the rule you created?

Apart from the limitations that were highlighted previously I'd expect that updating a custom field (of type date/time) with the current timestamp should work when doing a transition to either status of done, close, rejected.
Should the value in this exactly field be updated for all transitions you mentioned or are you planning to create a date-related field for done-transition, clone-transition and rejected-transition separately?



Thank you for your help. I change my mind and use standard JIRA. It's perfectly working. Now I just have to correct all the issues closed before ...


Like John Funk likes this
0 votes
Answer accepted
Fazila Ashraf Community Leader Jun 21, 2021


In JIRA, the resolution date is populated by JIRA when the resolution is last set on the ticket. If you set an automation to update the resolution value, that should update the resolution date.

@C. SIMON what I Don't understand is that when something moves to resolved. I edit the issue and change the resolution field to resolved, but the date does not appear, why?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events