Automation Rule run on a certain schedule creating a ticket for a list of Components

Question

Hello!  I am hoping you all can help me...  On the first day of each quarter I need to have a ticket created for a list of components.  I have about 200 components that I need to do this for so was hoping there was a way to do a FOR EACH branch.  But I can't figure it out. (I got the trigger, just cant figure out the component)

So Example:

COMP1

COMP2

COMP3

COMP4

On November 1st I want to have a ticket created that is the same except I want it for ONLY COMP2 and COMP3.

Any assistance would be greatly appeciated

Bill Sheboy · Answer

As you want to create issues for a list of components, you may store that list in a created variable, and then use that later in the advanced branch, by using split() to create a list.  That type of branch can use any smart value as a source.

For example...

* trigger: scheduled on your cadence
* action: create variable, as described here https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-variable* name: varMyComponentList
* smart value: Amazon Marketplace,Apache Kafka

* advanced branch:* smart value: {{varMyComponentList.split(",")}}
* name: varComponent* action: create issue...referencing {{varComponent}} as needed

Kelly Hansen_w1d7q2 · Answer

Im sorry Bill I am trying to follow what to do with the advanced branching but cannot figure it out.

The first step on Advanced branching is the Smart Value, which I am assuming is where I put my components, but what I am confused on is how do I enter my component values?  This is a screenshot of what I put together.  But I keep getting an error when I try to add more than one smartvalue.  Not to mention its not allowing me to have spaces but my component names have spaces in them.

Bill Sheboy · Answer

Thanks for that information, and...

The advanced branch can work from any smart values provided, not just from issues.  If you provided the components in a created variable (or smart value expression) that could still drive the branch.

You note a "sub component".  What do you mean by that?

Is it a subset of all possible components set up for your project, based upon a particular timeframe the rule runs?