Suggestions:

• "let me re-submit data to test changes"
• At save, the smart value syntax is validated. Errors are shown next to the rule components.
• At save, the rule components are validated for missing parts. Errors are shown next to the rule components.
• Bonus: where smart values can be entered, auto-completion is provided to reduce entry errors.
• Bonus: where null values can short-circuit smart values, warnings are shown
• Ability to validate JQL queries as the automation actor - Currently when using the validate query button with the JQL Condition element within Automation for Jira, the validation is run as the user triggering the issue. This may lead to false positive or false negative results if the Actor set for the automation rule does not have access to certain issues, projects or filters that the person running the validation query does. Either the behavior of the button should be adjusted to run as the actor since the automation rule will work differently in certain cases or utilize an additional checkbox to alter the behavior and run the validation as the actor.
• Ability to temporarily disable a component - Having the ability to temporarily disable or hide a component from running would be helpful for retaining it while testing other components or parts of an automation rule. By exploring different ways a component could be designed, one may need to compare and test different versions by creating multiple components and testing each one separately as part of the overall automation. Otherwise, deleting, re-creating and trying to remember where to insert it or what it's exact configuration was can be tedious and prone to errors.
• Ability to enable/disable A4J steps - It would be incredibly helpful if we had the option to add comments (similar to the "//" feature available in multiple programming languages) to the conditions and actions in automation rules. Currently, when testing a rule, the users often need to try out multiple scenarios with and without certain conditions. However, this process can be quite time-consuming as they have to manually remove or rewrite the conditions each time they want to test a different scenario. By implementing a comment or ignore option, they would be able to simply enable or disable a specific condition or action without having to modify the rule itself. This would save them valuable time and effort during testing.
• "when it works, great, if you have any issues it's impossible to debug"
• "demo the result of each step - for queries, show the result of the query"