Jira Automation - on page checks for syntax, correctness

[Purujeet Parida]

I have been trying to get an automation rule set up using a custom field (Reviewer) and the corresponding displayName, emailAddress, and a few date fields. Since I am not a pro at this, I am making some mistakes in choosing the right issue property or syntax or just usage and have to run the rule every time and go through the audit log to see what the issue was ("some errors")

Is it possible to have a check on syntax and/or feasibility of rule component/condition on the rule setup page itself? Sort of like the check we have in place for JQL (Which is an absolute blessing!)

Also, I noticed some of the useful descriptors around smart values are out of date now (considering the April 2019 changes described on the jira automation help pages). Is that correct for everyone or am I missing something here?

Fingers crossed I get my rule to work! Would like to be able to do it without triggering tens of mails/notifications which I have to then ask my users to ignore. #wishfulthinking?

[Jack Brickey · Accepted solution]

Those seem to be topics to provide as feedback to Atlassian. You might use the in-app feedback link.

One recommendation I would provide is to build your rule, particularly complex rules, in stages. Specifically if you send emails or notifications from your automation rules, disable those until you’re confident everything else is right. In this way you can ensure that people don’t get spammed while you’re testing your rule. Additionally consider adding the log action within your rule to log data that will help you troubleshoot your rule. In this way you won’t be flying blind or have to really dig in to understand the value of a field that was associated with an issue that triggered the event.

[Bill Sheboy]

Hi @Purujeet Parida 

Yes, and...to what Jack suggests: here are a couple of suggestions I added to help with rule writing and debugging:

• add a *verbose audit logging* option to automation rule details https://jira.atlassian.com/browse/JSWCLOUD-21615
• Validate automation rules before saving https://jira.atlassian.com/browse/JRASERVER-71196

One more thing to help: created variables.  You may use these to build up values/strings you plan to use later, such as in an email, and write them to the audit log first to confirm you get what you expect.

Best regards,
Bill

[Purujeet Parida]

Thank you @Bill Sheboy and @Jack - I wasn't sure if I was missing something, hence put in the question instead of suggestion. Log is a great suggestion, hadn't tried it, will try it out now.