Trying to auto-assign based on form cascading list selection

[tamsyn_brownie]

I am helping to update a form and work flow where we are re-designing our request form to contain a more navigable list of systems and then their sub-functions. Based on the selections made via the cascading list in the form, users can then also provide relevant links or are prompted to supply specific information related to the issue. 

For example: I have an issue in system A specifically in the Payment section, once selected a field will appear to request a link to the specific payments URL and include a customer ID. 

I am then trying to assign the issues created based on the Parent selection in the cascading list on the Form but am coming up short trying to identify how to do this in the Automations.

I can get as far as identifying the issue type and if the specific form has been submitted but not sure how to get to the custom selection of options within the Parent list. 

Any help appreciated!

[Deepak Jain]

Hello @tamsyn_brownie ,

Welcome to Atlassian community !!

Create an Automation Rule:

• Go to Project Settings > Automation.
• Click on Create Rule.

Set the Trigger:

• Choose a trigger, such as Issue Created or Field Value Changed (if you want the rule to run when the cascading field is updated).

Add a Condition to Check the Cascading Field:

• Click on New Condition > Select Field Value Condition.
• Choose the Cascading Field from the dropdown (the field that you want to evaluate).
• You can now set conditions for the Parent or Child values of the cascading field.

Add Actions to Assign the Issue:

• Click on New Action > Select Assign Issue.
• In the Assign To dropdown, you can either:
  • Choose a specific agent directly.
  • Use a smart value to assign the issue dynamically based on the cascading field value.

If you want to use different agents based on the different cascading field options, you can add multiple If/Else branches to the rule.

Example Automation Rule Setup:

• Trigger: Issue Created
• Condition:
  • If Cascading Field’s Parent is Support Type and Child is Level 1
    • Action: Assign to Agent John
  • Else If Cascading Field’s Parent is Support Type and Child is Level 2
    • Action: Assign to Agent Jane
  • Else (for other cases, if needed)
    • Action: Assign to a default agent or leave it unassigned.

Hope this helps !!

[tamsyn_brownie]

Amazing! I will try this - thank you!!!

[tamsyn_brownie]

@Deepak Jain I played with this and the Field Value Changed only comes up in the first step and not if I select Condition (either as Field Value Changed or Value Field Changed which I saw in another article) - my list of conditions to select stops at User Condition and the only F item is Form Used.

If I use it as the first trigger Field Value Changed I still cannot locate the name of the field as I see it on the form (I assume display name would be the one I'm looking for?). I also tried to add a Field Key but that doesn't appear either. 

Would this be a limitation of a team managed project?