Need the ability to set the created date on issues

[donhames]

As we install a new Agile-based standard template framework, we are creating new projects and copying or cloning the issues from existing projects into the new ones. There are several reasons for this, including the adoption of standardized schemes and the splitting or combining of projects. However, this approach has caused a problem with the creation date. When an issue is created in the new project, it is populated with the local timestamp for the date and time. This practice prevents us from retaining the historically created date from the original issues, which is essential for reporting.

Does anyone know of a way, such as a REST API, third-party app, or JQL, that allows the created date in the new issue to be reset to the created date from the original issue it was made from? To put it simply, can the created date in an issue be altered after it is created to allow it to be set to a date of our choosing?

I know this may not be a frequently asked question, but it nonetheless is intriguing and challenging to solve. Any takers?

I appreciate any help you can provide. 

[Agam Gupta · Accepted solution]

Hi Team,

My name is Agam from Atlassian and I'll be assisting you with this scenario.

You can update the Created date of an issue following the instructions provided in How to change the issue creation date using CSV import. These instructions document how to update the Created date of an issue that is already created to another date of your preference by creating a CSV file with the issue key, summary and the date to be changed which can then be imported.

I would recommend that you try doing this with a test issue first before performing it on other issues.

IMPORTANT: before you make any changes or follow the procedure, please ensure that you create and download a backup of your Jira Cloud site from https://toranotec.atlassian.net/secure/admin/CloudExport.jspa

Hope this helps! Let me know if you're having any trouble.

Regards,

Agam Gupta

[donhames]

@Agam Gupta  Thank you for your reply! I tried it, and it worked perfectly. It took a little time to build the import file, but only seconds to import. Thank you for sharing your wisdom!

Regards,

Don Hames

[donhames]

@Agam Gupta, I have a follow-up question for you. The article"Change work item creation date using CSV import in Jira" worked perfectly.

Now I need to update the resolved date. Is there a similar article for resolved date, or do you know how I can change it using a CSV file?

Hoping for an answer, thanks, Agam!

Don Hames

[donhames]

@Agam Gupta I should have mentioned that I found a similar article for changing the resolved date, but it isn't as detailed as the one for the created date.

I created a CSV file with the Issue key, Resolved, and Summary. I mapped them as:

Issue key -> Issue key

Resolved -> Date Resolved

Summary -> Summary

It runs normally, and it shows the correct resolved dates in the review screen before committing to the update, but the resolved date in the Jira issues did not change. The downloadable results file only shows that it updated the Summary field.

Do you have any idea what I might be doing wrong? Thanks again!

Don Hames

[donhames]

@Agam Gupta, In case this helps, here is a screenshot of the preview screen, and it shows the Resolved field in the CSV file will be imported as resolutiondate. Is that the correct field for the Resolved Jira field?

[Piyush Annadate _ACE Pune_]

Hello @donhames ,
As per @Agam Gupta  - approach would be get the exact dates, and use the 'external system import' - CSV option !

CSV having Issue Key, Summary and Date Created.
have dd/mmm/yyyy h:mm am/pm as date format (Always works).

Import that, it would update the same issues; if the listed issue key doesn't exist, it will create an issue. 

Make sure you have backup available (csv backup with all fields would be good as well).