How to change a resolved date in Jira

[Sian]

Hi all,

we recently did an import of +-250 stories into Jira as we moved platforms to track our ad hoc requests and wanted to see our historical data in Jira. However when we did the load the resolved dates did not upload correctly.

As a consequence we have now got resolved dates for 2025 and 2026 which is causing a huge issue with our reports. 

Is there anyway we can correct/change these resolved dates? Solution big or small is very welcome! 

Thank you in advance. 

Kind regards

Sian

[Tansu Akdeniz]

Hi @Sian 

You can also update imported issues Resolved Date field via csv.

Please check Updating existing issues section in this Import data from a CSV file.

Please try on testing environment first. If not possible, try with one sample issue then import all.

[Kamil Askerov]

Salam. @Tansu Akdeniz  is this working for jira cloud version?

[Hans Polder _Devoteam_]

Yes, you can observe this at the top of the page:

[Tiago Cardoso]

Expanding a bit on the correct, working answer from Tansu... as I struggled with it before making it to work.

• Open the external import experience in 
  • https://<your instance>.atlassian.net/jira/settings/system/external-import
• You must use the old import experience. The new import experience does not allow you to select existing projects (which scares me. Like, a lot).
• Before doing the update, create a filter with the minimum info you need for the update, like
  • Issue Key
  • Summary
  • Updated (I'll use this as the target date for resolution. Notice the format must match the format in Jira, like dd-MMM-yyyy)
  • Resolution (this information will be empty, as the items are empty)
• Download the data
• Update the "resolution" (empty) value to something meaningful within your context (like "done")
• Make sure the downloaded file format (based on above filter) is csv UTF-8. Notice Excel may use a "UTF-8 BOM", which isn't quite the same.
• When mapping the fields, map 
  • Key > Issue Key (needed to create a 1:1 connection)
  • Resolution > Resolution (if you don't provide a resolution string, the date isn't updated)
  • Summary > Summary (an update seems to not work without a summary)
  • Updated > Date Resolved (here's the trick, as I'm updating the "updated" date from my filter to the date resolved, implying that's the most accurate date related to that ticket)

Notice that by bulk updating the resolution, the updated date will be updated, which may trigger old items to appear in some Kanban / Scrum boards.

Hope this helps!

[Piotr Nawrocki]

Hello @Tiago Cardoso , do you know if it's still working? I'm trying to update resolution date using this method but it seems import is ignoring Resolution and Resolved Date completely

[Tiago Cardoso]

Not sure to be honest as I did this a while ago. It took me some time because I wasn't aware I had to provide a resolution information (done / cancelled / duplicated / etc). Check if that's not what's making this failing for you.

[NATHALY ALEJANDRA JARAMILLO AGUIAR]

Hi @Tiago Cardoso I followed the steps you mentioned, but it doesn't update my item; instead, it creates a new one. The information is entered correctly, but in a different item. Do you know what the problem might be?

[Tiago Cardoso]

Hi @NATHALY ALEJANDRA JARAMILLO AGUIAR - I can only think that the column mapping for the Issue Key may not be working properly. 

When using the CSV import, it's crucial to map the "Issue Key" field correctly in the import configuration. If the "Issue Key" is not mapped or mapped incorrectly, Jira may treat it as a new issue rather than updating an existing one. Ensure that the column for "Issue Key" in the CSV file is correctly associated with the "Issue Key" field during the import setup.

This could be checked by observing there the "issue key" information in your newly created jira has ended up on. Let's say it ended up in the summary or description, then we know that the issue key mapping isn't working properly.

Hope this helps!

[Dommalapati Chandrababu Naidu]

Hi @Sian ,

Welcome to Atlassian Community! 

You can do the bulk edit the issues. 

Navigate to filter and apply filter to find issue. in the top right of the screen you will find bulk change option in three dots. 

Checkout this link for the steps.

https://support.atlassian.com/jira-software-cloud/docs/edit-multiple-issues/

Thanks

[John Funk]

@Dommalapati Chandrababu Naidu  - The Resolved date field is not available through the Bulk change process.