We are in a situation where we need to change the creation date of some JIRA issues, so that Greenhopper can generate more accurate burndown chart for the project.
The reason is we created large amount of issues during the sprint, and we want to move them into the start of the project.
We found a way to change the issue creation date by updating jiraissue table in the database, but burndown chart remains unchanged in Greenhopper.
Does Greenhopper keep another copy of issue creation date? and how we can regenerate the burndown chart if we change the issue creation date?
Will appreciate it if someone can shed a light on this.
Did you stop Jira, run the SQL, restart Jira and then re-index it when you made the change?
Jira caches stuff, so you can't run SQL safely while it's running, and hacking the database (for issue data) always means the index goes out of line, so you absolutely need to re-index.
If you have re-indexed, then I'm not sure what the problem is, but I'd try the integrity checker next.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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