How to remove mistyped Estimate
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Please ensure that a backup have been done prior to the change below. Below modification is not guaranteed to be supported by Atlassian and any changes should be done in own risk
Symptoms
A mistype during the Estimate of an Issue during a Sprint is causing Burndown Chart to spike. See screenshot for example:
Cause
An Issue estimation input was incorrect. After updating the Estimate the Burndown Chart will still spike as it is a representation of the historical changes.
There is a request open for the ability to correct mistypes in the Estimate here: - GHS-8477Getting issue details... STATUS
Workaround
- The only way to correct this at the moment is through direct database modifications.
- Please be sure to shutdown JIRA and take a backup of your data prior to making any changes.
- Additionally, it is worth noting that Atlassian recommends correcting any mistype in the the Original Estimate by updating the Remaining Estimate field. With this approach, there is no negative impact other than the proportions on the Burndown Chart.
Since JIRA 6.1 the pkey column is no longer used. See instructions applicable to the version of JIRA.
- With this information we can now remove the rows in the changegroup table with id=11600 and 11601 and any rows in the table changeitem with groupid=11600 and 11601. These changes represent the initial mistype of 9 weeks in the Original Estimate field as well as the update to Remaining Estimate of 9 hours.
delete from changeitem where groupid = '11600';
delete from changeitem where groupid = '11601';
delete from changegroup where id = '11600';
delete from changegroup where id = '11601';
- Last step is to clear the contents of the <jira-home>/caches directory to rebuild the indexes. On next JIRA startup, please be sure to run a Re-Index of JIRA.
Please be sure to take a backup of your data prior to making any changes at the database level.