Project Automation

[Meghan Winters]

Hi all,

I am trying to create an automation rule that will populate sub tasks/ stories based on inputs selected in my intake form. There are multiple drop-down options that can be selected in the intake form. However, the rule seems to stop once the first value is read. Any ideas on how to change the syntax I am using in order to have the rule run all the way through and continue to populate subtasks?

I included a screenshot of the rule and questions in the form themselves below. Essentially question 17 is related to the size of the release we are working on (XL=1, L=2, M=3, S=4) and question 24 is related to what specific tactics we will be leveraging for the release. 

[Bill Sheboy]

Hi @Meghan Winters -- Welcome to the Atlassian Community!

To clarify the symptom, do you mean all of the data entered on the form is not available in the rule or that the rule does not process all of the steps that you expect?

1. If it is the first one: the issue created trigger can fire so fast that the data is not yet available.  The work-around for that is to add a Re-fetch action immediately after the trigger.  That will slow down the rule and reload the data before proceeding.
2. If it is the second thing, your rule structure may be preventing processing.  For example, after an earlier condition test, other things may not happen.  The solution for that is to use separate if/else clauses (or branches) for each section you want to process.

And if neither of these helps, please post an image of your complete rule as that may provide context.  One way to do that is with a screen capture that can scroll the entire browser window for the image.

Kind regards,
Bill

[Meghan Winters]

Sorry for the delay -- actually all set here!