Hi @Michael
You cannot control the resolutiondate field in JIRA. It takes the date that the resolution value was last updated in the ticket.
If you decide to update the resolution value through automation, it will autoset the resolutiondate to current date.
The usual way to do it is to set a resolution in a post-function on the transitions that go into status you consider "ended". You can do that with an automation as well, of course. But you're saying you want the trigger to be the change of status category. Automation doesn't have that available as a trigger, (it's not a field on the issue, it's an attribute of the status), so you'll need to do a bit of coding to be able to pick it up.
Yes, and...to Nic's answer...You could trigger on any issue transition, followed by an advanced compare condition before proceeding:
The rule will fire much more often than necessary, and avoids the need to name all the status values in the trigger.
Kind regards,Bill
I went this way in case anyone else needs to set resolutions
[JRACLOUD-65502] Import from CSV to Jira does not update Resolved Date field - Create and track feature requests for Atlassian products.
Is this a known bug? We are using automation to set the resolution to duplicate, but the resolutiondate is empty? We are on DataCenter.
Looks like this is known, but not really listed as a bug.
https://jira.atlassian.com/browse/JIRAAUTOSERVER-60
It's not a bug, or even a problem - the resolution date is intended to be the last time the resolution was set.
Looks like jira data center automation have same issue.
We tried to use automation :
It sets resolution, but does not set resolution date, even tightly linked to transition. Atlassian support told that there should be transition instead of Edit issue, but that is not an option as triggering transition is to the last status and no further transitions in workflow.
It looks like you're new here. Sign in or register to get started.
