How can I restrict an Automation rule to trigger only when an issue is created and not when it is cl

[Jyoti Kumari]

Hello Team,

Is there a way to restrict an Automation rule or a ScriptRunner behaviour script so that it triggers only during issue creation and not when an issue is cloned? It should not execute in the case of cloning.

Thanks and Regards,

Jyoti

[Utkarsh Agarwal]

Hi @Jyoti Kumari 

Jira Cloud links cloned issues to their originals by default using the “Clones / is cloned by” link type. You can use that as an indicator, but keep in mind that if the issue has been cloned multiple times, it might already have an existing Clones link.

For Automation:

• Trigger: Issue Created
• Add a Re-fetch issue data action (to ensure the link is created before evaluation).
• Add a Related Issues condition → Check for linked issues of type “Clones”.
• If you need to act only on newly created clones, you may want to also check the Created date or use Automation to tag the issue immediately when it’s first detected as a clone (e.g., set a custom field or label).

For ScriptRunner Behaviours:
Behaviours are designed for controlling field behavior dynamically on the Create/Edit screens, so whether the issue is cloned or freshly created doesn’t usually matter – they’ll run based on the field values shown on the form.

Kind Regards
Utkarsh

[Trudy Claspill]

It should be noted that when the Clone action is used in an Automation Rule it does not by default create a "clones/is cloned by" link between the source and new issue. That has to be explicitly added to the Clone action fields set. So if issues are Cloned through Automation Rules, that link may not be present.