We are using project configurator plugin for project export/import.
After we had done a project import, there are two permission scheme records occurred in nodeassociation table. So we need to delete that record and restart the JIRA server. Cause we cannot restart restart our server at will, wanna ask you how to avoid this, thank you.
That problem was reported as issue PCP-320 and a fix for it was released with version 1.7 of the plugin. So, I would recommend you to upgrade to the latest version of Project Configurator. However, you are running JIRA 5.2.X, which is no longer actively supported by the plugin, and the last version which runs on it is 1.6
Do you have plans to upgrade JIRA? Take into account that both JIRA 5.2.X and 6.0.X are now declared as "End of Life" by Atlassian. This would be the logical way forward.
Regarding the server restart, I would suggest this trick: after you delete the extra permission scheme record in the nodeassociation table, go to another project and change its associated permission scheme. Any project should do, if you do not want to alter permanently its associated permission scheme, change it twice: for example from scheme A to B, and then back to scheme A. See if that restores JIRA to a normal working condition without the need of a restart.
Hi all! My name is Miles and I work on the Marketplace team. We’re looking for better ways to recommend and suggest apps that are truly crowd favorites, so of course we wanted to poll the Community. ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs