Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

jira automation change the field "resolutiondate"

j.saceda October 7, 2022

I've created an automation rule in jira datacenter

In edit field these options:

the customfield is working but the resolution date not.

{
"fields": {
"resolutiondate": "{{now}}",
"customfield_31006": "the value I want to set"
}
}

 

The error obtained is the next one:

Edit issue

Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Resolved (resolutiondate)
Issues edited successfully
Do you know what I'm doing wrong?

2 answers

3 votes
Dirk Ronsmans
Community Champion
October 7, 2022

Most likely this is due to the fact that the resolutiondate is a system field.

You don't set that manually but by setting a Resolution value the date that you set that field will also be entered as your resolution date

j.saceda October 10, 2022

Hi Dirk,

thanks for your answer, but it's not working for me.

As you can see in the next screenshot

The resolutions are "Done", but the resolved field aka "resolutiondate" it's empty

Note, the resolution has been changed with an automation rule

Screenshot 2022-10-10 124516.png

Like Nika likes this
SKAdmin
Contributor
March 29, 2023

Is this a known bug? We are running into the same problem. Using automation we are setting the resolution to duplicate, but the resolutiondate is empty? We are on DataCenter. 

Rus Yates-Aylott
Contributor
October 4, 2023

The problem I have is that I have imported a large number of cases from Freshdesk. All these historical cases are now in JIRA.
However, the Freshdesk ResolveDate has not populated the resolutiondate in JIRA.
I have created a PowerAutomate API routine that can go and fetch that and populate a custom field in JIRA but there is no way of updating the reolutiondate field in JIRA with the historical resolution date from either the original Freshdesk case or the custom filed in jira. This is not useful when reports rely on that field to be correctly set.

Exporting & Importing cases seems to be the only option but I do not wish to risk that on a live system.


Surely dear Atlassian developers, you can do something to help in such a situation?

0 votes
Majken Longlade
Contributor
July 18, 2023

Looking for something else and found a few questions like this. I would think rather than using automation to set the resolution field, you'd want to use automation to transition the issue, then the transition will set the resolution and the date. 

Suggest an answer

Log in or Sign up to answer