To prevent 'Cloned Jira Work Item' from 'Exalate operation' when Trigger is in action

General Questions
1

From customer:

Is it possible to change the trigger somehow to only run on “Update/Change” issue, and not on
create? I have it set to specific project, custom field value and label value, but when a ticket is cloned it will actually Exalate the cloned issue when it is created.

3

As an alternate solution, we can this snippet into Outgoing Sync in the beginning, and here we are taking the keyword "CLONE - " from ‘Summary’ because when a Jira Work Item is cloned, so it adds that keyword unless a user is removing it, then it will unfortunately not work.

if(issue.summary.toString().startsWith("CLONE - "))
{
    return;
}
else
{
4

Hey @ashar.iqbal

Here you mention this solution may not work, Can you please share the script which is working ?

Thanks,
Sonal

5

From customer:

The work round in automation clearing the label would be a better solution, unless exalate runs before the rule. The rules will run on “Issue create” so depends who comes first.

In this scenario, the Exalate trigger executes immediately upon issue creation, which means it is evaluated before Jira Automation rules have a chance to run. As a result, even though the automation rule removes the label shortly after, the Exalate trigger has already fired and initiated the sync based on the original label.

Kind regards,
Ashar

1 Like