Automation / Clone with Related work item conditions

[Cristian Angel Bruner]

Hello community.

Im trying to clone issues only when NO related issues are associated to the item which triggered the automation flow. If there are already existint related issues, the work item must not be cloned.

The rule is an IF statement (also tried with WHEN) with the following condition:

• Related work items: Linked work items
• Link types: All types (also tried narrowing down to related to)
• Condition: are not present

Below the condition > Clone the work item into another project

The problem is that the work item is being cloned ALWAYS

The first trigger (assign to) clonse and links the issue (related to).

The second trigger, when i reassign, altough there is a related to item, its cloned again duplicating the issue.

Any suggestions?

Thank you.

Cristian

[Cristian Angel Bruner]

Hi Thorssten and Bill

Thank you for your reply both of you.

What im trying to solve is :

The trigger happens and clones the item when one specific team is assigned to it.

If the work item goes back and forth to different teams, i wont to avoid the cloning again when it comes back to the same team, as it must happen one unique time.

I assumed that the Linked work items condition would help with this. If its lconed and linked, it should create a new clone. But it does not work. 

Nevertheless, I have been able to solve this, but not with the Linked items condition but directly with a JQL issueLinkType is EMPTY

[Bill Sheboy]

Hi @Cristian Angel Bruner -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

• what problem are you trying to solve with this rule; that is, "why do this?"
• what type of project is this: company-managed, team-managed, JPD, etc.
• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Until we see those...

In my experience, the Related Work Items condition for testing links can produce unexpected results.  It may be better to use the Lookup Work Items action with JQL to test that no items exist with your criteria, and validate that with the Smart Values condition to check the count returned by the lookup.

Kind regards,
Bill

[Thorsten Letschert _Decadis AG_]

Hey @Cristian Angel Bruner

Would you mind adding a screenshot of your rule? I assume a problem with the actual placement of your components, which is rather challenging to determine verbally.

Besides, when you speak of a "second trigger," you're referring to the rule being triggered again, right?

Regards,
Thorsten