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

[Brent Mills]

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

[Brent Mills]

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

[Ramiro Pointis]

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

[Ramiro Pointis]

You could always give it a try (if you dare). I have made a lot of changes in the database, always in a time that no one is using the jira, nothing bad happened yet. Obviuosly atlassian doesn't take responsibility if something wrong happens. I think, not totally sure! but if you reindex after doing the modification. And if something goes wrong you can change the ids again and reindex, again.

A very important thing is to do a backup, so you can restore if something goes too bad.

Remember that if you do this, it should be in an time that no one uses the Jira. Good luck if you decide to do that, and post here your solution. This is pretty interesting :-)

[Nic Brough -Adaptavist-]

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.

[Radu Dumitriu]

No, AFAIK you will mess the DB if you would do only that.

You will have to change it on existing issues too and on default values (at least, if I remember well).