Can't update resolve date

lucabartoli

Hi all,

I tried to update the resolve date by API but the field apparently can't be set.

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

So I tried with the CSV import method but I had some issues:

1. UTF-8 chars error

My file contains chars like ù, à, ...

Seems like those chars are not recognized by the import tool, which ask for an encoding (UTF-8) but it is unable to parse the dataset (it complains about non-ASCII chars, makes no sense).

If I replace those chars with ASCII ones, I can go further, but this leads to problem 2.

 

2. Import fails and doesn't update tickets

This is the error, but I don't know why

Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state: At least one given IssueParentAssociations must not be empty!

 

Can anyone help?

Is there any other (possibly easy) method to update this field?

 

Thank you all

Dario B

Ciao @lucabartoli ,

The only way to change the resolution date to already resolved issues is by using the CSV import method described in below links:

• https://jira.atlassian.com/browse/JRACLOUD-65502
• https://community.atlassian.com/t5/Jira-questions/Is-there-a-way-to-change-the-quot-Resolution-Date-quot-in-Jira/qaq-p/385739
• https://community.atlassian.com/t5/Jira-questions/How-to-bulk-change-resolution-date-instead-of-just-status-of/qaq-p/189104

 

As per the "Is there a way to change the "Resolution Date" thread in the Atlassian Community, in order to update the resolution dates you need a CSV file with at least the below 4 fields:

1. Issue Key
2. Summary
3. Resolution
4. Resolved (to be mapped to "Date Resolved")

 

However, please notice that this only works when using External System Import (in the administration section of your Jira instance), as documented in: Importing data from CSV

Performing the CSV import from the issue search page, as explained in: Creating issues using the CSV importer, does not work.

 

Once this has been said, in order to answer your points:

1. You should not face any character encoding issues if you export the desired issues from Jira to CSV (only the mentioned fields) and then re-import the same CSV file after modifying the Resolved field. 
2. The error message is complaining about parent-child link being empty while at least one should be present. Are you updating sub-tasks? Which fields do you have in the CSV file you are trying to import?

 

 

Cheers,
Dario