How to change the issue resolution using a database update

Still need help?

The Atlassian Community is here for you.

Ask the community

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.


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.


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.

  1. Backup the database
  2. Query the resolution table to determine the ID of the resolution you want to set
  3. Join the jiraissue and project tables to get the proper ID of the ticket you're modifying
    1. example:

      select * from jiraissue ji join project p on where p.pkey='TEST' and issuenum='12'
      tip/resting Created with Sketch.

      This would return the issue details for the issue ticket: TEST-12

  4. With that information, you can update the resolution column within jiraissue table to the proper resolution ID value
  5. Once updates are complete, you will need to trigger a project re-index for the related tickets
    1. Following my above example, a project re-index will need to be triggered for project TEST

Last modified on Nov 14, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.