Update to cloning of ScriptRunner settings when cloning a repository

In addition to the below bug fix [SRBITB-424] regarding the correct cloning of ScriptRunner settings (i.e. pre-hooks, post-hooks, merge checks and event handlers), we have also made the following changes to the feature:

The above changes were made to make the cloning of a repository more robust and secure in all circumstances. If you no longer need a ScriptRunner setting applied following a repository clone, they can be retrospectively deleted or edited for the cloned repository.


For how-to questions please ask on Atlassian Answers where there is a very active community. Adaptavist staff are also likely to respond there.

Ask a question about ScriptRunner for JIRA, for for Bitbucket Server, or for Confluence.