Back date an issue's start date

[Andrew Nisbet]

Hi, Is there a way to back date an issue's start date to some time in the past? We are converting an existing project into Jira, and want to carry over records of the completed issues.

Thanks

[Nic Brough -Adaptavist- · Accepted solution]

That depends on how you define "start date".

The "created" date in Jira cannot be altered via the UI if you're using that, but if you are importing data from another system, most of the importers will let you set it.

If you're using a custom date field, then yes, you can edit that any time.

If it's a derived field of some sort, then you'd need to look at the data behind it.

[Moustafa_Saif]

At the time of Networks or telco-grade incidents, especially while emergency or critical incident happens the Operator (like Telenor, Vimplecom, Airtel, etc.) operations team may not have time to create a ticket neither the solution provider engineer where everybody jumping to solve the issue. 

Therefore, after the problem was solved, it requires backdated activities like ticket creation, remedy and resolution provide, etc for which need to match the time according to the problem time. 

In JIRA service desk, I don't see any backdate activity tasks to do. This backdates activity is a standard task in TT management system in the Telecommunication services.

Atlassian need to incorporate this in JIRA formally.

[Nic Brough -Adaptavist-]

So create a custom field for "backdated creation date".

The vast majority of Jira systems do not need such a date, and those who do have the ability to add a custom field to capture it.  If Atlassian did this for every field that was essential to a tiny number of users, you'd have a default issue create screen with 500 fields on it.   So Atlassian are not going to put it into the core of the system.