Problem: We have a custom field that our engineers select to show how many "impacted system" (50+) there are in the ticket ( 2 stories created under the epic) What I have so far: * Trigger: When issue transition from "To Do" to "In progress" * For each: smart value based on "impacted system" (Use 2 as an example)* **Audit log for "impacted system" returned as 2. * Then: Create a new "Story" in Same project. What I expect: * 2 stories should be created Actual: * 1 story was created I am missing a requirement between "For Each" and "then"? any help is much appreciated it!

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

Automation for JIRA - Create multiple stories based on values of a multiple selected custom field

Garret Zhang

Problem:

We have a custom field that our engineers select to show how many "impacted system" (50+) there are in the ticket (<-Epic).

What I want to automate is that after an issue is transitioned from one status to another, a number of stories is created based on how many "impacted systems" there are. (example, 2 impacted systems -> 2 stories created under the epic)

What I have so far:

Trigger: When issue transition from "To Do" to "In progress"
For each: smart value based on "impacted system" (Use 2 as an example)
- **Audit log for "impacted system" returned as 2.
Then: Create a new "Story" in Same project.

What I expect:

2 stories should be created

Actual:

1 story was created

I am missing a requirement between "For Each" and "then"? any help is much appreciated it!

Accepted answers

Trudy P Claspill

Hello @Garret Zhang

Please show us the details of the rule you have constructed. What is the smart value you are using in the FOR EACH component.

The "value" of that smart value might be 2, but that doesn't mean that you have specified a smart value that is recognized as have two values.

All comments

Trudy P Claspill

Hello @Garret Zhang

Please show us the details of the rule you have constructed. What is the smart value you are using in the FOR EACH component.

The "value" of that smart value might be 2, but that doesn't mean that you have specified a smart value that is recognized as have two values.

Garret Zhang

Hi @Trudy P Claspill

Thank you for the quick response! The smart value is off of the custom field "SystemImpacted" which had multiple selections. In my testing, I selected 2 values.

Here is the audit log:

Trudy P Claspill

The "size" attribute is a single value which happens to tell you there are multiple values in the parent object "ImpactedSystem". So the branch is working "correctly" - there is only one value for "size" to be used in the branch.

Instead you need to be using {{issue.ImpactedSystem}} in the Smart Value field.

Garret Zhang

@Trudy P Claspill That fixed it! Thank you so much!

Trudy P Claspill

You're welcome!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation