Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hi, In one issue the story point was mistakenly entered 60,000 instead of 60. which has corrupted the whole version report, even the value was changed back to 60. Is there anyway that the Version Report can be forced to read the updated data instead of the old one. Please see the attached screenshot.
Agile reports are dependent on issue history. Though you updated the version in the issue, the issue history might not change.
You need to update that particular history item which shows version as 60000 by running SQL query on JIRA database.
Hi Bharadwaj, Thanks for the response, will it help if i will delete the issue? I would have checked it but we do not have the pre-prod environment to check. i can only suggest to team for the deletion if i am quite sure. Thanks again.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That should fix it, yes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register Now
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.