-
Suggestion
-
Resolution: Duplicate
-
0
-
Description
Currently, when you rename Request Types on your project, any Automation Rule that have a condition referencing a request type will not be updated and will break.
It is necessary to manually modify all automations that have Request Types referenced to the new names, and that might take a lot of work depending on how many rules there are in the instance, and how many request type's name were changed.
- blocks
-
AUTO-468 Support for field IDs instead of just field names in Automation, so rules don't break when fields are renamed, and to support custom fields with the same name
- Gathering Interest