How can I update resolved date for Subtasks that are already closed

[Swati_Mathapati]

Jira project administrators changed the Subtask workflow and somehow ended up closing Subtasks without resolution date set.

I tried setting up resolution date in Scriptrunner  console with the code

mutableIssue.setResolutionDate(new Timestamp(..))

but the resolved date is not updated. Nothing shows up in logs either.

[Max Lim _Adaptavist_ · Accepted solution]

Did you "save" it after you set it? Like:

import com.atlassian.jira.event.type.EventDispatchOption

mutableIssue.setResolutionDate(new Timestamp(..))

ComponentAccessor.getIssueManager().updateIssue(ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser(), issue, EventDispatchOption.ISSUE_UPDATED, true)

[Swati_Mathapati]

Hi @Max Lim _Adaptavist_ ,

Thanks for the update.

We did try with the below code and it doesn't work

IssueManager issueManager = ComponentAccessor.getIssueManager()
DateFormat dateFormat = new SimpleDateFormat("MM/dd/yyyy hh:mm:ss");
Date date = dateFormat.parse("03/23/2021 06:00:00");

long time = date.getTime();

Timestamp targetDate = new Timestamp(time);

MutableIssue missue = (MutableIssue) issueManager.getIssueObject("SARTRACKER-946")

missue.setResolutionDate(targetDate);
issueManager.updateIssue(ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser(), missue, EventDispatchOption.ISSUE_UPDATED, true)

[Max Lim _Adaptavist_]

This is one of the fields that can't be modified in newer version of API, for good reasons.

My guess is that it was modifiable with MutableIssue.store() and it is now deprecated.

Deprecated. 
Use the Object's Service or Manager to save values. Since v5.0. DO NOT USE THIS as it overwrites all the fields of the issue which can result in difficult to reproduce bugs Prefer to use QueryDslAccessor to change only needed fields

I do not recommend it.

[Swati_Mathapati]

Thanks we are out of Ideas now.

[Daniel Garcia]

what are the good reasons ?

How is csv import different ?

[Dario B]

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.

Cheers,
Dario

[Jeff Abbott]

I am using Jira v8.4.2. CVS import does not work in that version, but Script Runner does.

[Dario B]

@Jeff Abbott ,

Please notice that this worked for a lot of other customers in all the linked threads (as well as for myself) and that it has been officially documented as the resolution of:

•  [JRACLOUD-65502] Import from CSV to Jira does not update Resolved Date field 

Saying this is not correct because it didn't work for you, without providing any further detail on what you tried and/or what failed is not really useful. 

[Daniel Garcia]

I think this question was about jira server

[KAGITHALA BABU ANVESH]

Hello @Swati_Mathapati ,

Resolved date will be appeared based on the resolution chosen date.

Create a self transition on "Closed" status. and Edit Transition and place "Resolution" field on that Transition.

Select all the issues and Bulk Transition is the option to choose the resolution.

As of my knowledge , we can't edit resolution date for past date.

Thanks,

Anvesh