how to create a for each branch without branching out from main when creating rules?

[Nancy Tsai]

Hi,

I'm trying to follow the instruction from a  solved issue in Jira Automation, but I have problem adding a "For each" without branching out from main when creating a new rule. 

This is the what the rule should look like in when creating new rule in jira automation. 

                                                 

But somehow when I want to add the "For: Stories" branching, it doesn't let me stay on the main branch and branch out instead, seepicture below. What should I do to get the result like above picture? 

[Trudy Claspill · Accepted solution]

Hello @Nancy Tsai 

What you are seeing is just a new graphical presentation for displaying a Branch. The affect/functionality is actually exactly the same in both representations.

[Bill Sheboy]

Hi @Nancy Tsai 

Yes, and...to Trudy's answer:

Remember to add that Clone Issue action before the Create Variable one to get that scenario to work as expected.

If your scenario is different than that example rule, please disregard.  Thanks!

Kind regards,
Bill

[Nancy Tsai]

@Trudy Claspill For, should I add the last" Then: Clone issue in to same project" under the "For each branch" or under "Then: create variable"? 

It just looks a bit confusing for me if I try to follow the solution based on the method in Solved issue. 

[Trudy Claspill]

The "Then: Clone issue" action should be added within the "For each branch" step, where you see "Add to branch".

In the older graphic all the items I've indicated with the curved line are within the branch. The get executed for each issue identified by the For step. This is indicated by them being aligned on a vertical line that is indented under the For Stories. The steps within the branch will execute only if the For step finds issues that match its conditions. In this case the steps will be executed only if the For step finds child issues in the Epic.

The "For" step itself is at the same level as the main path of the rule, as indicated by its icon being on the same vertical line on the left as the other main path steps.

In the new graphic they are indenting both the For step and the steps within in. The indicate that the For step itself is still part of the main path by showing the line connected to the main path (1). The steps within the branch, that are executed only if the For conditions are met, are connected only to the For step and not to the main path (2).