Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
I have JIRA issue (and probably more) that created date for shows as 09/Jan/16 5:13 AM while first change history item is marked as happened in 09/Jul/15 8:55 PM !!!?
Is that a possible case? is it something wrong in the DB?
It is wrong, but it is possible to do it accidentally.
The usual culprit is an import. If your import data for an issue contains a created date, that can be any value - the importers are not there to judge your data, they'll simply import it. That means you can future-date the issue creation and then have history entries that pre-date the apparent creation.
The other methods would be database hacking, scripts doing the wrong things, or bugs (although I don't know of any date bugs in JIRA or the bigger add-ons that might do this)
So, there is something wrong in your database, but generally, it won't actually cause you any problems, other than some graphs and reports looking a little bit odd (or possibly crashing if the add-on can't handle it)y
I'd fix it by running a one-off script to find and update the dates, although you'd need a way to identify them and a rule for what dates to put into "created"
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs