Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
If I understand correctly, the following may help:
1. Create a new field that will be used as the selection drop down for the user and give it some default values:
2. Create a new automation script (yes automations = scripts and scripts = automations) and ensure it has the "field-display" tag:
In the above script, the returned list options assumes that the field named "monitored_field" is available in the incident and that it is a list. It will also only display options for the field if it is part of an existing incident and not in the "create / new" incident form.
3. Assign the field-display script to the field:
4. Create a new "field-change-triggered" script and make sure to assign the "field-change-triggered" tag:
In the above script, if the selection has changed then the script runs the playbook again by simply setting the playbook. When setting with no parameters, it re-runs the existing playbook on the existing incident.
5. Edit the field again and this time assign the field change parameters:
This means that each incident will have a field (that you can place in the incident layout) that will contain dynamic content based on the incident fields, lists or context and when changed will execute a command (in this case the playbook re-run).
A small demo:
In your use case, the field-display script would pull a list of parent incidents. The field-change script would then re-assign the current incident to that parent incident.
I hope this helps.
Regards
Adam
