nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Create an alert for cloned tickets.

Francisco Navarro_zsedh7

Dear community,

I'm trying to create an alert automation for the creation of a "Bug" issue. The alert isn't a problem creating, but the problem I'm having is how to know if the issue has been cloned from another project (this is what I need to filter).

In short, the automation should send an email to X user when the bug is cloned from a certain Jira SM project.

Thank you in advance for the guidance!

Accepted answers

John Funk

Hi Francisco,

The first thing we need to know is what happens that is unique to that process so we know what to base the trigger on. Is this a manual clone or a clone by automation? Or is there some other indicator (binary) that when the cloned issue is created that we know for sure that is the issue we need to base the trigger on?

arielei

Hey @Francisco Navarro

If the work-item is cloned, then the linked issue will be filled by the original work-item.

So you can create an automation:

1. Trigger = created work-item

2. If issuetype = Bug and Linkeissue type = Clones

3. Action = send email.

Prachi Bolar

Hello,

Welcome to community here

Screenshot 2025-06-23 at 8.16.33 PM.png

So the send email trigger would have below

A new Bug issue has been cloned from an existing Bug.

Cloned Bug Key: {{issue.key}}
Summary of Cloned Bug: {{issue.summary}}

Please check the new issue for further details.

When there is an existing issue with the type bug, you will get an email which will give you details of the cloned issue. so when you open the cloned issue, it would show from where this issue was cloned

example

Screenshot 2025-06-23 at 8.18.44 PM.png

Screenshot 2025-06-23 at 8.19.24 PM.png

YOu can try something on this lines

Thank You,

Prachi

All comments

John Funk

Hi Francisco,

arielei

Hey @Francisco Navarro

If the work-item is cloned, then the linked issue will be filled by the original work-item.

So you can create an automation:

1. Trigger = created work-item

2. If issuetype = Bug and Linkeissue type = Clones

3. Action = send email.

Francisco Navarro_zsedh7

Hi John,

Cloning is automated from a Jira SM project. After a target team is selected to resolve the bug, the automation clones the issue (in the Jira SM project, it's a task, and cloning it transforms it into a bug).

Francisco Navarro_zsedh7

Hi Arielei,

I created another automation with your steps, but it doesn't perform the action. I'm sending you an image of the log. I first performed this test without activating the rule box "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule" and then activated it. In both cases, it did not perform any action.

Prachi Bolar

Hello,

Welcome to community here

Screenshot 2025-06-23 at 8.16.33 PM.png

So the send email trigger would have below

A new Bug issue has been cloned from an existing Bug.

Cloned Bug Key: {{issue.key}}
Summary of Cloned Bug: {{issue.summary}}

Please check the new issue for further details.

example

Screenshot 2025-06-23 at 8.18.44 PM.png

Screenshot 2025-06-23 at 8.19.24 PM.png

YOu can try something on this lines

Thank You,

Prachi

John Funk

Okay, modify your rule above to put in a Re-fetch action (or two) after the Create trigger. What is probably happening is that the work item gets created and before the other automation is done to link the tickets, this rule is firing the IF condition. Have it slow down a little in between with the Re-fetch and see if that works. If one doesn't, then try two (or put in a Delay action of 5 seconds or so).

Francisco Navarro_zsedh7

Thanks for the guidance. I finally created one based on the Summary, which meets my needs.Thanks for the guidance. I finally created one based on the Summary, which meets my needs.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

jira-service-management