How to change updated field for issue?

Russ Frazier

We had to move data from a next-gen project to a classic project and found that the "updated" field for completed issues was all changed to the date of the move instead of being preserved. Turns out the version report uses "updated" for completed issue dates and it would be hard to explain this chart to management now, as many Done issues are now apparently Done on one date.

How can I change the updated field in the many Done issues so it reflects a more accurate history? I've tried import csv with various config files and curl with both an update JSON and with overrideEditableFields=true and it either doesn't recognize the field or the permissions are insufficient. I'm not sure either one of these is completely correct. My understanding is that the admin user has the correct permissions.

Attempt at using curl to change the "update"field:

curl -D- -u admin_user:auth_token -X -PUT --data @json_update -H "Content-Type: application/json" https://<our_name>.atlassian.net/reset/api/2/issue/<ISSUE-NUMBER&gt;



json_update:

{
"fields": {
"updated":{"date":"10/01/2019 12:30 PM"}
}

}

Output error message:

{"errorMessages":[],"errors":{"updated":"Field 'updated' cannot be set. It is not on the appropriate screen, or unknown."}}



Attempt at using overrideEditableFlag to obtain list of editable fields:

curl -D- -u admin_user:auth_token -X GET -H "Content-Type: application/json" https://<our_name>.atlassian.net/rest/api/3/issue/<ISSUE-NUMBER>/editmeta?overrideEditableFlag=true

output error message:

{"errorMessages":["Only Connect add-on users with admin scope permission are allowed to override the editable flag."],"errors":{}}

 

Thanks

Nic Brough -Adaptavist-

The "updated" field is calculated from the last time an issue had its data changed (project is one of the items that saves the date, along with all the fields, status, comments and so-on.  From memory, it's only links that don't cause an update)

On Server/DC you can use code or even amend the database if you must, but on Cloud, you cannot do anything that deep inside Jira.  I'm afraid your updated timestamp is going to remain the calculated value.