Hello,
I’m working on a Jira automation where we need to create multiple issues based on selections made in a multi-select dropdown field (such as “Size”). For each selected value, a separate issue should be created, and each should have the correct Request Type and starting Status.
In our implementation, it leads with the for: dropdown.size branch, and creates new work items as expected. However, I cannot use normal status and request type actions to properly define them as desired. I understand through previous automation experimenting that adding a second branch, that uses created recently will not work as expected, as branches run in parallel. This leads to the Request Type and Status not being set correctly on the new issues.
I wanted to reach out to the community for advice on how to handle this. Is there a more efficient method that ensures the correct fields are applied without branch conflicts?
Additionally, a potential issue with our current execution is it creates a parent work item that contains all the selected options. Is it possible to add into this implementation an archiving that will hide this from the main workflow? I do not want to impact the children work items.
Thank you in advance,
Josh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.