Automation - set resolution & resolution date

[Michael]

Looking to create an automation rule to set the resolution and the resolution date by when the issue moves into the status category of done. 

Has anyone setup or configured a rule like this before? Any help is appreciated 

[Nic Brough -Adaptavist- · Accepted solution]

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.

[Bill Sheboy]

Hi @Michael 

Yes, and...to Nic's answer...You could trigger on any issue transition, followed by an advanced compare condition before proceeding:

• first value: {{issue.status.statusCategory.name}}
• condition: equals
• second value: Done

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

[Fazila Ashraf · Accepted solution]

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. 

[SKAdmin]

Is this a known bug? We are using automation to set the resolution to duplicate, but the resolutiondate is empty? We are on DataCenter. 

[SKAdmin]

Looks like this is known, but not really listed as a bug. 

https://jira.atlassian.com/browse/JIRAAUTOSERVER-60

[Nic Brough -Adaptavist-]

It's not a bug, or even a problem - the resolution date is intended to be the last time the resolution was set.

[SKAdmin]

Correct, but when the resolution is set via automation the date isn't set if you use edit. It's has be in set as a part of the transition to work. 

[Nic Brough -Adaptavist-]

Ah, yes, that's a quirk of the way you are doing it.  Jira only calculates the resolution date as part of the transition that closes the issue.

Why are you setting a resolution instead of resolving/closing the issue?

[Fazila Ashraf]

Can you re-confirm that you are observing that behaviour?

I recently used the automation in my cloud instance to set the resolution and it also set the resolutiondate as current date.

[Clayton Taylor]

I am seeing that resolutiondate is not getting set via Automation using Jira Data Center; it appears there is a discrepancy between functionality in DC and Cloud.

We are trying to use Automation to replace Workflow post functions on a large enterprise account so that project admins have control over their projects and do not have to involve sys admins. The overhead is very expensive to centralize and manage Jira instances across ~100 projects, so more capability in Automation would be preferred.

[Renni Verho]

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. 

[Michael]

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.