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

Create Tickets Based on Custom Field with Multiple Entries

Jecynta Ogeto

I am trying to create new, linked tickets dependent upon the custom field "Part Number" in the parent Issue. The "Part Number" field may contain one part number or several. Is there a way to parse the part numbers in the "Part Number" field to create the new tickets? Screenshot 2024-05-13 151420.png

Accepted answers

All comments

Kalyan Sattaluri_iinm1n

Hello @Jecynta Ogeto

If you expect it to be comma separated string, to parse and convert to list, you can use {{Part Number.split(",")}} smart value.

Not sure of your end goal, but If you are in cloud, you can use "Advanced Branching" - For/Each and give a variable name (mypartnumber) and value to iterate on as {{Part Number.split(",")}}

once inside the branch, you can create issues/link etc and you can use {{mypartnumber}} to reference each value while creating issues for example.

Please try and share screenshot/audit log if stuck.

Bill Sheboy

Hi @Jecynta Ogeto -- Welcome to the Atlassian Community!

What version of Jira are you using: Cloud, Server, or Data Center?

With Jira Cloud, you may split the values in the field and loop over them with an advanced branch. Please look here to learn more about that approach:

However if you are using Jira Server or Data Center, they do not have advanced branching yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-749 One possible workaround is a rule which repeatedly triggers itself using an Incoming Webhook technique, progressively removing one value at a time from the list until done: https://confluence.atlassian.com/automation/jira-automation-triggers-993924804.html#Jiraautomationtriggers-incomingwebhookIncomingwebhook

Kind regards,
Bill

Jecynta Ogeto

Thanks for responding so quickly. When I tried this, I got this error in the Audit log.

Screenshot 2024-05-15 093435.png

Here's a pick of the rule setup.

Screenshot 2024-05-15 093511.png

Kalyan Sattaluri_iinm1n

Hello @Jecynta Ogeto

You need to share your Advanced Branch step for this error.

But before you do,

add log statements like I have in the below screenshot and,
share your rule which shows Advanced Branch details like I have including audit log.

Because without the log statement, we cannot tell anything.

Finally, when creating new issue, you need to use {{mypart}} in your summary if you want to reference item which is in loop. We will get there, but first insert these log statements, run the rule and share audit log and rule which shows advanced branch like Ihave.

Jecynta Ogeto

Here's what I have so far. Screenshot 2024-05-15 151410.png Screenshot 2024-05-15 151443.png