Link existing work items according to a specific workflow

Question

Hi,

I created the following situation:

Automation rule number 1: Create a number of work items according to a specific amount of process steps.

=> Everything works fine here

Now I want to link every created work item according to a specific workflow. Like 1,2,3 =>4=>5=>6=>7. But sometimes it's just 1,2 =>4=>5=>6 or another time just 3=>4=>5=>6. The idea ist the process steps are not always the same and so the tickets are not the same any time.

But here is my problem:

Automation rules number 2-n:

As you can see. The rules finds the correct work item. ("1 work item found"). I checked and it is the correct one.

But when I run the rules. This happens:

Because in this case there were 4 process steps, also 4 of the "linking automations" started. But number 3 (first screenshot) that previously found the work item while testing, does not find anything (see audit log => step 3).

So, why is this happening? 
Any ideas?
What do I miss?

Looking forward to your answers. 
Thanks!

Regards

Trudy P Claspill · Answer

I see that you opened a separate Question asking about alternatives to the Delay action for use in Free and Standard Jira Cloud plans.

https://community.atlassian.com/forums/Jira-questions/Best-way-of-delaying-a-branch-execution-in-Free-or-Standard/qaq-p/3162812

Simon Huprich_uyj8zt · Answer

Hi @Trudy P Claspill
This sounds possible. The Problem is that I am on a Free or Standard Plan and as the documentation is mentioning "Delays" are only available for Premium and Enterprise. 
Any idea to delay the execution of the branch with other options?

Trudy P Claspill · Answer

So the issue that is being sought in the second rule was created by the first rule, correct?

Again, looking at the log from the second rule, the second rule was triggered 4 times. The second triggering of that rule, at 18:55:43, is the one that tried to execute the branch.

If it had correctly found the related issue, which of the issues shown in the log would it have found; MK-235?

If so, perhaps there is a timing issue and the indexing has not completed for the first issue, resulting in it not being found when the JQL executes during the second run of the rule.

Perhaps try adding a Delay action in the second rule immediately after the trigger and before the Branch.

https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Delay