Template (Epic) Cloner for Jira - Problem Clone with Field Conditionned with Script Runner

[Deleted user]

Hi, 

We have a problem with Add-On Template (Epic) Cloner for Jira.

We can't clone a Epic with Task, 

This task has a field that is not always displayed depending on the project where it is located.

This field is a list
If we do a dupplication for a project that does not have the display of this field, clone it and refuse as this field is mandatory in the screen system. This display condition is configured with Script Runner.

We must select this field and select "Aucune". But Users of this project don't know this field, this problem can't create incomprehension and mystake. It's not friendly 

Template (Epic) Cloner for Jira does not seem to take this script runner configuration. Can you help us with this resolution?

[Michal Zawalski · Accepted solution]

Hi @[deleted]!
Michal from Vilisoft here.

Reffering to our private mail conversation about the problem - we will post here our response to that problem for future visitors of the topic:

"We checked your scenario and we are afraid that you would need to add extra conditions to your scripts or set up the fields as an optional.

In our plugin when issues are cloned JIRA native functions are used to create new issues. It means that if field is mandatory in your JIRA, to clone issue all required fields must be populated.
Hope you will fix it and our plugin will speed up your management work."

[Deleted user · Accepted solution]

We exchanged with editor

No solution is available for this topic.

This add-on doesn't run when a condition of script runner is active