Is it safe to change the ID's of priorties in the database?

Question

We modified the values for our priorities, which assigned them new ID's in the database.  We depend on a third party integration that uses the default ID's for connection.  My new ID's are 6,7,8,9,10.  Does anyone know if there will be consequences in changing them back to 1,2,3,4,5 with a sql update script to the priority table?

thanks, brent

Nic Brough -Adaptavist- · Answer

It's not just "when no one is using it" - you really should take Jira down while runing database changes.  It caches some things in memory which it will happily write back to the database and wipe out your changes.  So don't run SQL while Jira is running.

Ramiro P · Answer

Mark the answer as correct. That way you can help the other users.

Brent Mills · Answer

Here is a detail what happened.  I have an integration with Utest which depends on the default priority ID's.  When we modified our priority values we did not rename them, but created new ones and deleted the old ones.  This appended new ids, so instead of 1,2,3,4, I now had 6,7,8,9, which utest did not like.

in order to get the 114 issues from their system to ours I updated our ids to match what they expected in the priority table.  As we had several issues that had the old id's  i next updated the jiraissue table with the new ids.   So far so good.

thanks, Brent