+1

+1

+1

The "Clone Plus" option in Jira Cloud sets the reporter to the person who is cloning. Clone Plus also resets some fields to empty, e.g. Fix versions etc.

@Kristen:

Take care about the syntax. In the comment it's written

• triggerIssue.issuelinks.type.name

But you need to use it with brackets
 

 {{triggerIssue.issuelinks.type.name}} 

Also i think it's better to user the id because maybe some users translated "CLONERS" to their own language in the jpm.xml

This way you get the ID:

 {{triggerIssue.issuelinks.type.id}} 

And can compare it to 10001 (please check if 10001 is cloners also in your system, but i think this is default).

Best Regards

Manuel

For some reason this doesn't work for me.  The error in the log says the issue doesn't match the condition.  

Thanks Michael, it works. I wanted to have the above works only if i clone bug not for story, epic etc

Yes Please! I just had a request for automation that will copy the Summary field to a custom field on the new ticket upon cloning.

Michel's answer works like a charm, but I beat my head against the wall for an hour before I  noticed the critical 'Re-fetch issue data' step!

A possible workaround for this, could be using triggerIssue.issuelinks.type.name that should be Cloners for cloned issues: