I had this problem when I was writing an initializer script for one of the custom fields in my JIRA instance.
Found a piece that isn’t well documented. But as usual, I’m explaining my steps and then the solution. It’s no real big deal anyway. 🙂
JIRA to JIRA project migration — most of the time this has been a headache when it comes to customer negotiations and compromises.
So, this is loosely another part of the unofficial series ‘fixing a corrupted JIRA db‘.
However, this is a different case. This JIRA instance (7.1.x) was created by importing a huge XML backup (> 1 million issues). Due to an unknown reason, ActiveObjects didn’t import. That means, JIRA Software (aka JIRA Agile) no longer functioned normal.
Yesterday I blogged about how to fix JIRA Permission Schemes of a corrupted JIRA database. The observation was from atlassian-jira.log, but in my case I soon found out the problem was much greater in my case.
Edit (24 May): Spoiler alert! There’s a better way.
I came across a corrupted JIRA database with all projects lost their permission schemes.
If you are a JIRA system administrator, have you ever come across the requirement of partially exporting JIRA into XML – probably for importing individual projects into another JIRA instance?