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; } } }

Automation creates duplicates when cloning

Alex Dokhtiar

I have pretty simple automation with the following logic:

When issue in project X is transitioned into certain status then this issue is cloned into the other project.

Here is how it looks like:

Screenshot 2024-11-07 at 10.56.00.png

I have added an additional check for linked issues to ensure rule is not triggered when issue was already cloned once. This rule works fine when I create an issue in "Open" status and then transition it into "PROD investigation".

The problem appears when status 'PROD investigation' is chosen during the issue creation. In this case issues is cloned twice meaning that by some reason rule is triggered twice.

I've tried adding delay before "Then", tried setting 'from' statuses in the trigger and couple of other options and nothing seems to work.

Am I missing something? Thank you in advance.

Accepted answers

Alex Dokhtiar

With the help of @Bill Sheboy I've managed to make it work. You'd need two separate rules: for creation and for transition.

Screenshot 2024-11-12 at 17.39.29.png

All comments

Laura Pellizzari

Hi,

looking at this problem at the source. Why not restrict it to just the "open" status when creating the ticket?

regards

Laura

Bill Sheboy

Hi @Alex Dokhtiar

When an issue is created in a status other than the first in the workflow, it does that in two steps:

create the issue
transition the issue

This can be observed in the issue history.

Do you have two rules, where one is triggered on Issue Created and another is on Issue Transitioned? If so, for this scenario you would not need the Issue Created rule.

If that is not the case, please post:

an image of the complete audit log entries and
images of the audit log details for two rule executions for the newly created issue

Kind regards,
Bill

Alex Dokhtiar

Hi @Bill Sheboy , thank you for the reply.

I don't have two separate rules, by some reason trigger happens twice within this automation.

Here is an image of the audit log within the rule Screenshot 2024-11-08 at 11.13.29.png

It appears that, for some reason, the rule is being triggered not only on transition but also on creation, which shouldn’t be happening and I don't know how to avoid this from happening.

Alex Dokhtiar

Hi Laura,

You are right, it can be done, but due to the nature of the workflow, tasks can be created in other statuses as well.

Bill Sheboy

Thanks for that information and I just recreated the symptom. I found this open defect for the symptom: https://jira.atlassian.com/browse/AUTO-916

I hypothesize the root cause is in the updated REST API endpoint for issue create as it may be raising the event twice: once on create and once on transition. Worse still for your scenario, the cloning adds linking (which is another slow operation) and so passes the condition due to rule timing problems between the two rule triggerings.

The workaround in the defect is not helpful: disable the feature to allow transition on create.

Some other workarounds to try could be:

after the trigger, add the Re-fetch Issue action (rather than using the Delay one) to both slow the rule and reload the data
rather than using the Related Issues Condition, do this in two steps to perform the check
- use Lookup Issues with JQL to get the possible existing clone
- use the Smart Values Condition to test that {{lookupIssues.size}} equals 0 before trying to add the clone

Alex Dokhtiar

Hi Bill, thanks a lot for your help. It makes total sense now. I will try mentioned workaround next week and post the update.

Alex Dokhtiar

With the help of @Bill Sheboy I've managed to make it work. You'd need two separate rules: for creation and for transition.

Screenshot 2024-11-12 at 17.39.29.png

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