Jira Automation create issues based on two multi pickers

[Bent Möller]

Hey, I try to use Jira for documenting Permissions while using two multi pickers (one for users, one for the permissions).

This is what I want:

A User creates an Issue, inside the Issue 3 Permissions are request for 2 Users.

So you have: User 1, User 2, Permission 1, Permission 2, Permission 3

Now for reasons each documentation issue may only contain a single User and a single Permission. So running the Automation on this example should result in 6 issues:

• User 1 Permission 1
• User 1 Permission 2
• User 1 Permission 3
• User 2 Permission 1
• User 2 Permission 2
• User 2 Permission 3

At the moment I cant find a solution for this. Only workaround I found for now is restricting the User field to a single picker and then only referencing the Permissions multi picker. This, however, is very inconvient when a new permission is introduced that requires the initial documentation of dozens of Users.

Another way would be building this functionality directly into the Workflow via Scriptrunner which might work, but is inconvinient as well.

[Bent Möller · Accepted solution]

I probably found the solution.

It is actually possible to put a branch inside a branch. To do this, you have to Configure your first branch. Then add a Component -> select branch -> DO NOT MAKE FURTHER CHANGES -> drag&drop the unconfigured branch into your configured branch -> configure the second branch.

Following my example, this automation will now create 6 issues each with the respective user and permission name in the summary using the {{Permission}} and {{User}} variables I created with the branch.

[Bill Sheboy]

Hi @Bent Möller 

First thing, I doubt that is supported behavior and may stop working (or not work as you expect.)

I recall similar community posts about multiple levels of nesting for if / else blocks and branching, using drag-and-drop for incompletely defined actions.  Often such rules would fail to work as expected or become unsavable if they were ever edited.  The ability to drag-and-drop such components in the editor appeared to be a symptom of something wrong in a particular site, which then required Atlassian Support assistance.

There are open suggestions to add such types of nesting, and none of them appear to be in progress.  I also do not see any new articles announcing such nesting.

On a final note, I tried what you described in several ways and it did not permit me to drag one advanced branch within another.

Kind regards,
Bill