How to change the issue resolution using a database update
The content on this page relates to database updates which are not supported by our Atlassian Support Offerings. Consequently, Atlassian can not guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.
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
Purpose
Sometimes an incorrect resolution may have been set for an issue and may need to be modified without causing the resolution date to be changed. This article covers how to do this using a database update.
Resolution
Database updates are not supported and can result in integrity issues. Please ensure to test this before applying to production. We recommend to use the CSV import functionality to re-import issues with proper dates.
- Backup the database
- Query the
resolutiontable to determine theIDof the resolution you want to set - Join the
jiraissueandprojecttables to get the properIDof the ticket you're modifyingexample:
select * from jiraissue ji join project p on ji.project=p.id where p.pkey='TEST' and issuenum='12'This would return the issue details for the issue ticket: TEST-12
- With that information, you can update the
resolutioncolumn withinjiraissuetable to the proper resolution ID value - Once updates are complete, you will need to trigger a project re-index for the related tickets
- Following my above example, a project re-index will need to be triggered for project TEST