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.
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.
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.
Introducing Jira Cloud for Excel Here at the product integrations team at Atlassian, we are thrilled to announce the new Jira Cloud for Excel add-in! This add-in lets you export Jira data directly ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events