How to remove an excessive number of records in the resolution field

[Olga]

Hi, 

When we imported tasks into Jira, we added „resolution date” to wrong field - "resolution". Now we have 3000 records with date in "resolution" field. :( 

As a result, I have to wait a 20-30 seconds for the list with hints in the field „resolution” on the "issue navigator” to load.

How can I fix this? 

 

[Florian]

First fix your issues. To do this write a filter in JQL that gives you a list and perform a bulk change.

• You need permission to do this (permission scheme, ask you admin if necessary).
• The resolution field needs to be on the edit screen I think. Otherwise it cannot be changed.
• If bulk change does not work use "Automation for Jira" this will do the job.

When this is done you can go to Settings -> Issues-> Resolutions and delete them manually. Perhaps there is a faster way to do this directly on the database.

Something like this might work:

DELETE FROM resolution where pname like '%.%.2019 %:%'

But be aware. Changes in the database might cause unpredictable side effects.

• Your issue history might get broken and show unknown resolutions
• Jira caching might not refresh (restart Jira after modifying something in the database)

[Florian]

An take a look at this: https://confluence.atlassian.com/jirakb/how-to-change-the-issue-resolution-using-a-database-update-872279120.html

This might allow you to change the resolution without writing the change history.

Again: Be aware of the consequences!

[John Funk]

As Florian said, you can do that with the Bulk change functionality mentioned above. But since you are using Jira Cloud, you do not have access to the database to make changes. So the Bulk change is the best way to go.