The new Automations UI is causing a range of issues, some causing serious delays and double-work in projects / templates (submitted to Support but posting here for Up Votes 
). Overall, the new UI is heading in a better & more advanced direction, but
-
Most urgent issue - New Automations continues to rename rules. After putting a name in, Automations will rename it. The automation then has to be edited with the correct name, and still does not always save. When creating templates from projects, for instance, it renamed ALL automations with the exception of those in a bundle; now, all automations have to be renamed again within the template after renaming them in the project. Example photos attached of a project with correctly named rules that was turned into a template, and all rules were renamed by the system.
-
New Automations does not always recognize when an automation is ready to save, and does not give a signifier of why it may not be ready to save (missing condition, etc.). Sometimes it will not save even if all fields are filled out, then changes have to be discarded and the rule has to be reedited. In some cases, the rule has to be completely recreated because it will not save changes on an existing rule.
-
UI for rule builder in Bundles, My Tasks, and other areas has not been updated to the new Automations UI. Not a huge issue for creating rules, but confusing for clients.
-
Automations seem to run much slower than previously, with some automations trying to automatically include AI when AI has not been selected in the rule or is not necessary. This only seems to happen in workspaces with AI enabled.
-
Exiting out of an automation takes you back to the Customize menu and not the Automations menu, and also automatically expands the left sidebar navigation, adding multiple clicks to get back to Automations. If Customize or Automations is open and you minimize the left sidebar, it closes out of the menus and you have to click back to Customize → Automations.
-
New automations reorders rules as you update them, and does not always keep your manual reorder. There is no way to select how they are ordered automatically (i.e. alphabetical, manual, by rule type, etc.). But, reordering them manually does not always stick.
-
Broken automations cannot always be edited & saved. When deleting a field that was a condition within an existing rule, the rule becomes broken (obviously). When editing - removing the condition - the rule still shows as broken. Removing the branch entirely & rebuilding still shows the rule as broken. The rule then has to be deleted and rebuilt from scratch.
-
Every automation step has to select the app and does not default to Asana. This adds significant clicks when building complex rules. It would be great if it defaulted to Asana, and then you can click to change to a different app. This would reduce the majority of clicks needed (at the very least) for Asana-focused rules. This is not adding a step for selecting other apps, since in its current state, either Asana or other app has to be selected.
