Atlassian - Please Support a "Unload" method for the BulkOperationManager Class in the Atlassian SDK

Lars Broden July 17, 2017

Hi Atlassian

The below support issue popped up and even though we can provide a workaround through a Jira Server restart, it would be more appropriate to supply a "Unload" method for the BulkOperationManager Class. We are not alone with this problem, tested it on several other plugins as well.

Scenario:

1. Disable Bulk Clone Plugin (Manage Add-Ons) (Jira 7.4.1, Bulk Clone Professional 4.7.1)

2. Go to Search for issues, choose a search filter

3. Go to Bulk Operations

4. BulkClone.operation.properties pops up without a label and an option to Clone

5. Forcing a Clone generates a 404 Dead Link Error

6. Restarting the Server, Issue in Point 4 disapears and everything is as expected

 

- Atlassian - Could you please provide guidance on how to get around this (If possible), possibly provide a "Unload" method

************************************************************************************

 

Hi,

We have done some extensive testing on this now and the issue apears if you disable the plugin and then try to do a Bulk Clone operation, it looks messy and if you still trying to force a Bulk Clone operation, you will get a 404 error. If you enable the plugin again it looks normal, as expected and works as expected. If you want to keep the plugin disabled and not having the issue above, please RE-Start the server and the issue will go away.

We are using BulkOperationManager in the Atlassian SDK and it does not unfortunately have a method to unload the component: https://docs.atlassian.com/jira/7.1.6/com/atlassian/jira/bulkedit/BulkOperationManager.html


We tested with some other plugins that provide bulk operations and the same happens with them, so it is not a Bulk Clone issue, rather a Atlassian SDK issue, but can be bypassed as described above.

0 answers

Suggest an answer

Log in or Sign up to answer