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

Jira Automation: Creating multiple linked issues based on Multi-Choice Custom Field

Mohamed Sarjun_ltvwrk

Hi guys,

I need help with a Jira automation rule for a project that has the following issue types:

Request

Epic

Story

Sub-task

I have an Issue Collector that creates a Request issue, which includes custom fields related to Epic and Story issue types.

Requirement:

When a Request issue is created, I want an automation rule to:

1. Extract values from a custom field called Category Type (a multi-choice select list with multiple options).

2. For each selected value in Category Type, create:

A Epic issue (linked as a child to the Request).

A Story issue (linked as a child to the respective Epic issue).

3. Ensure all issues are linked properly to maintain the hierarchy.

I have already set up an automation rule, but it is not working as expected:

I am using branching and smart values, but the branch rule is not getting executed. Error: Unable to run this component

Could someone help me identify what's wrong and suggest the correct smart values or rule structure?

Thanks
Sarjun.

Accepted answers

Evgenii

Hi, @Mohamed Sarjun

Welcome to Atlassian Community

What is returned in variable {{CategoryType}}?

And if I understood right, you are trying to receive list of values, and work with each of them?

In case of list values it's better to use list iteration, like described here:
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/

It will iterate through all elements in field value and use values in actions.

Made an example

Bill Sheboy

Hi @Mohamed Sarjun

Starting with the original rule you show in the question, when you created the variable, that leads to a text value such as this:

Option A, Option B, Option C

Where using {{issue.customfiled_12663.value}} automatically added a comma-space delimiter.

To then use that to feed the Advanced Branch, the values must be split back into a list:

{{categoryType.split(", ")}}

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#split-String-separator-

As an alternative, you could use the smart value directly to feed the branch:

{{issue.customfiled_12663.value}}

The values in the branch will be the text of the options selected for the field.

Kind regards,
Bill

All comments

Evgenii

Hi, @Mohamed Sarjun

Welcome to Atlassian Community

What is returned in variable {{CategoryType}}?

Made an example

Mohamed Sarjun_ltvwrk

Hi @Evgenii

Yes, you understood it correctly. The variable {{CategoryType}} holds a list of values selected in the Category Type custom field (which is a multi-choice select list). My goal is to iterate through each value in this list and create separate Epic and Story issues for each selected value while maintaining the correct parent-child hierarchy.

However, I am facing issues when trying to extract and work with individual values from this list within the automation rule

Evgenii

I made an example, attached images above. I think, it's your case, and it will solve your problem

Mohamed Sarjun_ltvwrk

I tried implementing the same branching rule as suggested, but I am still encountering the same issue: "Unable to run this component." It seems like the iteration is not working as expected in my case.
rule 5.png rule 4.png
Are there any additional steps I should take to ensure the list values are properly processed within the branch?

Bill Sheboy

Hi @Mohamed Sarjun

Starting with the original rule you show in the question, when you created the variable, that leads to a text value such as this:

Option A, Option B, Option C

Where using {{issue.customfiled_12663.value}} automatically added a comma-space delimiter.

To then use that to feed the Advanced Branch, the values must be split back into a list:

{{categoryType.split(", ")}}

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#split-String-separator-

As an alternative, you could use the smart value directly to feed the branch:

{{issue.customfiled_12663.value}}

The values in the branch will be the text of the options selected for the field.

Kind regards,
Bill

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

jira-automation