Since our upgrade to JIRA 6.3.5 and BulkClone 1.0.11, JIRA users receive an error 500 when they browse projects from the "Projects" menu. The error disapears when the add-on is disabled.
My workaround is to enable bulk clone for a minimum amount of time after setting up all the clones we need to do then disabling it again. It's not a great solution but it makes more sense than cloning 300 Tests by hand for a new project.
It would however be nice if you could select an option for no emails. Sending people 300 emails when you clone a test plan isn't needed. You can work around this by making your Template Project access limited to a few admins but then you lose the ability for users to add and modify the templates.
+1 we are facing the same problem on JIRA 6.3.9. Kindly update any tentative date by which there will be a fix for this issue. Need to upgrade JIRA to install JIRA Service Desk module and not having bulk clone on the latest version of JIRA will be a blocker for us proceed further with the upgrade..
A fix is now in place with BulkClone 1.0.13.
Please empty the plugin cache after upgrading and also the Browser cache.
Shutdown the JIRA server and empty the server cache and then restart again
If the problem still persists, please provide us with the relevant portions of the JIRA log that causes the exepction
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
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