Need Help: Automation: if I add component x to epic, create two user stories BRD x and UAT x but if

[rachel rutti]

Need Help: Automation:

If I say Condition:  Field value changes

For field Component

For Edit Issues

Where do I select if "value is added" to field?  Does anyone have that Option?  I do not see it.  

Googling says

• Crucially, for "Change type," select "Value added." This ensures the rule only triggers when a new component is introduced, not when existing components are removed or modified.

This is exactly what I need, but can't seem to find it.  Can anyone else see this option?

Does anyone else have the "Change Type" of "Value Added"?  We do not seem to have it or can't find it.

[Trudy Claspill]

Hello @rachel rutti 

You should see that as part of the Trigger:

If you are not seeing that, please provide a screen image of what you are seeing.

[rachel rutti]

Hello my friend Trudy!!

Thanks.... I am looking...

[rachel rutti]

Hmm... we do not have Change Type.... I can't seem to paste screen shot, but I can select Components field, then the next field is 

For....

[rachel rutti]

I was looking to see if it would be a different Trigger, but don't see it there either.

[rachel rutti]

It looks like maybe it was disabled or is there somewhere I can look to see why that option would be turned off?

[Trudy Claspill]

As far as I know there is not an option to disable that.

Does your screen otherwise look the same as mine? Do you have the same icon showing for the trigger? I ask that to try to confirm that you are actually working with Jira Cloud. If you are working with Jira Data Center the available options are different, the screen looks different, and the icons look different. The option is not available in Jira Data Center:

[rachel rutti]

I think we went through this before trying to figure out if we were Jira data center or not and possibly we were .....  Still trying to get an image here.  yes, icons are the same... green Field value changed...

I can select component in fields to monitor changes

Then the next field drop down is your 

For....

and the options are Create Issue, Edit Issue, Transition Issue, Assign issue.

If you select Edit Issue, it just gives the option to execute immediately or not 

Then Save.

[rachel rutti]

I read some other google answers saying we had to do a branch rule and check if the user stories already existed and if the answer was no, then create them.

I tried this but it kept spinning, as I likely did not have the exactly correct syntax.

The problem with the options we seem to have is that 

1) it works to create 2 specific user stories each time a specific component is added - great.

2) problem is... we don't have a clause to check if user story already exists and if so, don't create it... so on the 2nd and 3rd components added to Epic, it re-creates the first and second set of user stories.  (for the first and 2nd component)

This is what I googled and tried, but it just spun, but Maybe I could work on syntax.

Here's how to achieve this:

• Trigger:

  Set the automation rule to trigger when the "Components" field of an Epic is updated.
• Condition (Check for Specific Component):

  Add a "Field value changed" condition or a "JQL condition" to check if a specific component has been added. For example, if adding "Component A" should create "Story X," ensure the condition specifically checks for the addition of "Component A."
• Condition (Prevent Duplicate Story Creation):

  This is the crucial step. Before creating the story, add another condition to check if the desired story already exists under that epic.

  • Related Issues Condition: Use a "Related issues" condition, branching to "Stories (or other issues in Epic)."
  • JQL Condition within the Branch: Within this branch, add a "JQL condition" that checks for the existence of the specific story you want to create. For example, summary = "Story X for Component A" AND "Epic Link" = {{issue.key}}.
  • Invert the Condition: Crucially, set this JQL condition to "No matches" or "None of the above" to ensure the action only proceeds if the story does not already exist.
• Action:

  If the conditions are met (the specific component was added and the corresponding story does not exist), then execute the action to "Create issue" (the user story).

Example Rule Structure:

• Trigger: Issue updated (Field: Components)
• Condition: Issue fields condition: Components contains "Component A"
• Branch rule / related issues: Stories (or other issues in Epic)
  • JQL Condition: summary = "Story X for Component A" AND "Epic Link" = {{issue.key}} (set to "No matches")
• Action: Create issue (Story X for Component A)

By implementing the "Related issues" branch with a JQL condition that checks for the absence of the specific story, the automation will only create the story once, even if other components are subsequently added to the same epic.

[Trudy Claspill]

Looking at one of your previous questions:

https://community.atlassian.com/forums/Jira-questions/Std-JQL-how-to-get-parents-and-children-of-my-query-for-stories/qaq-p/2782731

...we concluded that you were using Jira Data Center. So you are likely seeing something like the second image I provided, and you won't have the option to specify "value added" as part of the trigger.

It will be very useful if you include that information in any future questions you post.

To help you debug the rule you have at this point we need you to post images of the current rule. Otherwise we would need you to provide all the details in a text description including explaining the structure of any steps that are nested 

[rachel rutti]

Yes, sorry, I thought I replied right away that we had discussed Data Center in the past and that it was likely that.... and finally got image to post.  But sorry for any inconvenience.

[rachel rutti]

That was the basic rule I created that I posted and it just spun.  Do you see anything incorrect in it at initial glance?  It wouldn't stop spinning to I had to refresh, and lost it, but If you think that is the only solution, or the best option so far, then I will re-create it.  Do you think that is the best option? 

[rachel rutti]

If so, I will work on it and we can, as you say, debug if necessary. 

Re-looking at it now, maybe my mistake was thinking this was some syntax (haha) oops 

 (set to "No matches")

....and I think all it was trying to say was that clause would be false.

But, since you brought up the Data Center, does it appear this is the only or best option to get this to work?

Thanks, I'll start on it and get back.

Appreciate you!

[rachel rutti]

Okay, I did several different iterations of this changing clauses to summary ~ and !~ 

and moved the clauses to be under each other like parenthesis in different ways, but still did not create an BRD IM user story.

So.... we have....

Green icon

When Value changes for 

Components

Orange icon

If Issue type equals 

Epic

Orange icon

And: Components contains any of

xxxxx

Purple Icon

For Stories (or other issues in Epic)

             Indented

              If Issue matches JQL

               summary ~ UAT IM or summary ~ BRD IM            ( I tried both !~ and ~)

              Then Create a new 

                Story

               in 

               same project

[Trudy Claspill]

What do you mean by "it just spun"? Did that happen when you clicked the Publish button?

There are multiple problems with the rule that you say your searches advised you to use. Maybe I'll go over those problems later.

This is the rule I recommend you try. In my example the Component of interest is "JIRA".

After the trigger add a condition to make sure that the trigger issue is an Epic. Otherwise it will be run when Components are changed for other types of issues.

Then there is the condition to check that that the Component value of interest is in the Epic.

Then use a Condition: Related Issues: JQL. For the Related Issues field select JQL. For the Related Issues JQL use what I have shown. That tells Jira that you want to look at all the child issues of the Epic that triggered the rule.

For Condition choose None match specified JQL.

For Matching JQL use a JQL statement that would match the issue you want to create. Since the Condition is "None match" this condition will Pass only when the Epic doesn't have an issue that matches the one you want to create.

Following that is the last step to Create the new issue.