Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to use a Manual Trigger with multiple inputs and dynamically generate a list for adva

Asier Vadillo June 6, 2025

Hi everyone,

I'm currently building a Jira Automation rule where I want to manually trigger the rule and select multiple values (like checkboxes representing versions or environments). Based on the selected inputs, I want to dynamically create a list of selected values and use Advanced branching (For each) to iterate over each of them.

The idea is:

  • Use a manual trigger with multiple checkbox inputs (e.g., 24Q3, 25Q2, etc.).Screenshot from 2025-06-06 10-53-29.png

  • Automatically extract only those which were selected (i.e., their value is true).

  • Create a list/array like ["24Q3", "25Q2"].

  • Use this list in a "For each" branch in the same rule.Screenshot from 2025-06-06 10-54-09.png

However, it seems that:

  • The manual trigger input is returned as an object (e.g., {24Q3=true, 25Q2=true, 26Q1=false}), and Smart Values don’t provide a way to loop through object keys or filter them dynamically.

  • I can't find a way to transform the selected values into a usable list for the advanced branching.


💡 What I'm looking for:

  • Is there any workaround that allows dynamically collecting only the selected checkbox inputs from the manual trigger into a list format (["24Q3", "25Q2"])?

  • Or, is there any recommended pattern to simulate dynamic For each execution based on manual selections?

Any ideas or examples would be greatly appreciated!

Thanks in advance 🙏

1 answer

1 accepted

2 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 6, 2025

Hi @Asier Vadillo 

The {{userInputs}} data appears to be a JSON set of fields, and cannot be iterated over directly.  A workaround is use a created variable, and then split(), filter, and parse the results as needed.

For example:

  • trigger: manual, with your user inputs
  • action: create variable
    • variable name: varUserInputs
    • smart value: {{userInputs}}
  • something that needs the input fields selected as checked / true
{{varUserInputs.substringBetween("{", "}").split(", ").match("^(.*=true)").substringBefore("=true").asJsonStringArray}}

How that works is:

  • from the created variable, remove the curly brackets
  • split() the result into a list
  • use inline, list iteration with the match() function and a regular expression to find the checked ones
  • and then extract the field's variable name using the substringBefore() function
  • finally, use asJsonStringArray to format as you described

Please adjust as needed for your expression.

 

Kind regards,
Bill

Asier Vadillo June 9, 2025

Hi @Bill Sheboy ,

Thanks you for the response!

I implemented a different workaround where I built the list "24Q4",25Q2" and iterated over it using .split(","). But your process seems fine to me.

I did delay my response because of:

Screenshot from 2025-06-09 10-46-48.png

regards

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events