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

How can I create stories using Jira automation without duplicates

Rita Arellano

Hi All,

So, I found how to create stories with Jira automation, but I keep getting duplicates. So I have 'Component' field instead of 'Teams.' I have a total of 6 'Components' that can be added to an epic at any time - and it can sometimes just be 1 Component or many. The rule I created keeps returning duplicates. This is my use case:

Anytime the 'Component' field is edited - meaning when a new 'Component' is added at an epic level - create a story for that component and prefix the summary of that story with the team's Component.

Rule:

I created two seperate rules, because I thought it be easier, but no.... So I have a rule for Component = X and Component = Y

Please let me know how can I avoid duplicate stories and have a story created each time a Component is added to the epic - the story must have the Components prefix:

Rule X

Accepted answers

Bill Sheboy

Hi @Rita Arellano

You could first check if the issues exist before creating them...

When using multiple rules, one for each component value, you could first check if the issue already exists (using JQL or Lookup Issues and checking the found issues), and only created it when it does not exist.
When using one rule, with repeated current issue branches (one for each component field values), and perform the same check for the presence of the issue before creating it.

Also, what do you want to happen if a component value is removed?

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Rita Arellano

You could first check if the issues exist before creating them...

When using multiple rules, one for each component value, you could first check if the issue already exists (using JQL or Lookup Issues and checking the found issues), and only created it when it does not exist.
When using one rule, with repeated current issue branches (one for each component field values), and perform the same check for the presence of the issue before creating it.

Also, what do you want to happen if a component value is removed?

Kind regards,
Bill

Rita Arellano

@Bill Sheboy

Is this something close? I am only focusing in the creation of the stories, if a component gets taken out the epic - that will be something I will tackle later, but first, I added the check of duplicates before the action of creating stories, but that is not yielding any stories now, any advise from here on out?

X V2.jpg Y V3.jpg

Bill Sheboy

To clarify a bit, what does "duplicate" mean for the scenario:

another issue exists with specific text in the Summary field
something else?

If it is the Summary check, perhaps try this:

trigger: value changes for Components
branch: to current issue
- condition: component contains "X"
- related issues condition, with JQL: no issues exist with "X" in the Summary
- action: create your issue
branch: to current issue
- condition: component contains "Y"
- related issues condition, with JQL: no issues exist with "Y" in the Summary
- action: create your issue
...repeat as needed for different components

The branches help isolate the logic for each block.

Rita Arellano

I tried some variation of what you have proposed and its working a bit better, no longer getting duplicates. But I still have an issue. Please see the following scenarios below. Thank you in advance for your time.

1. Component X is entered in Epic = Passes - story gets created correctly

2. Component X and Y entered in Epic = Passes - both stories get created correctly

3. Component Y is entered in Epic = Passes - story gets created correctly

4. Component Y is entered first then component X in Epic = Fail, two stories for Y are created upon entering each component and X does not get created.

How can I have it in where it does not matter which 'Component' is entered first - story gets created for each component regardless of sequence entered? Issue with Y.jpg

Bill Sheboy

Please note in you rule you are using two different conditions:

if Component / s equals (in any order)...
if Component / s contains any of...

I believe you want to use the contains condition for all of your tests; otherwise it will only look for an exact match to the values noted.

Welcome!

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

Quick Links

Find more posts tagged with

jira

automation

data-center

jira-software-data-center