You may need to follow that procedure when you need to update resolution dates when for some reason, the tickets were not correctly « closed », from JIRA’s POV at the right date. I had that issue due to an error in our workflow, causing the ticket to have the « Done » status but resolution date not updated.
To update these dates, first:
Prepare a CSV with all issues you want to update, wether they’re already in a resolved « Done » or not. The CSV should contains the following fields:
- Issue key
Then, with the following field, go to :
You need to have certain privileges to access this page & make updates on issues. Choose « CSV ». That brings you to the following page:
Update your CSV & click Next. You can use the advanced mode to change some import parameters.
In the following step, you can choose wether to update/import issue to a defined project or to have the project defined in the CSV. In my case I have only one project to update.
Then the important part is the date, because you want to update the date 🙂 so be careful to clearly set the Date format mask corresponding exactly to your date format and don’t trust Jira date format by default, it may be wrong (he didn’t parse your file to recognise it ;))
In my case, my date was « 29/09/2019 11:44 » so I had to update the Jira mask to
instead of the
"dd/MMM/yy h:mm a"
proposed by default.
Click on Next. Time has come to map fields
Then click on Next and it’ll bring you to the « Begin import » button.
Click on « Begin import » and wait a bit. Here is the result I got for one story update
Hope it helped cause it wasn’t that easy to find, especially the right place to import the CSV & the date trick due to wrong default value (in my case).