Create an alert for cloned tickets.

[Francisco Navarro]

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!

[Prachi Bolar]

Hello,

Welcome to community here 

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

YOu can try something on this lines 

Thank You,

Prachi

[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]

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.

[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? 

[Francisco Navarro]

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).

[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).