How to restrict cloning for an Epic

Question

Team,

As we have Scripted fields and few linked issues created through automation rules at feature level, we want to restrict the cloning of feature to avoid conflicts:

Note: I found a workflow property to restrict cloning. The problem with this approach is as we have different epic workflows, a lot of status, adding it to all statuses will take time and effort, do we have any other alternative approach for this like using API's or permission scheme?

Nic Brough -Adaptavist- · Answer

Hi Arunajyothi,

The way you suggest - ploughing through all your workflows and adding the property you need is by far the best option for doing this.

Scriptrunner Behaviours only works with issue fields, it can't block the use of system functionality.

But as you say you are on server, there is one other thing I would look at.  Scriptrunner fragments can be used to hide existing elements of the UI, as well as their original purpose (adding elements).

I have not tried it myself, but you should be able to use fragments to (conditionally) remove the clone link from the screens.  A determined user would be able to work out a URL directly, but removing the link will stop 99.9% of your users, as they won't know, or want to make the effort of doing it.

I should warn you, the language in Fragments is very "Jira developer" oriented - if you've never delved into writing Atlassian apps for Server/DC, it looks arcane and not really related to what you see on the front-end.  Heck, I've suggested the whole thing gets renamed from "fragments" to something that says "mess with the UI" more clearly.  Also, a lot of people miss the "fragment finder"  - that should really be the starting place - it can help you find the bit of the UI you want to mess with!  The DC Scriptrunner team currently have an active project to re-vamp the whole of the fragments functionality (better layout, better language, and able to do more)

John Funk · Answer

Hi Arunajyothi,

Sorry, but I am not aware of another way to do this. Maybe the ScriptRunner Behaviours app would have this functionality, but certainly there is nothing out of the box.