What's the point of changing the automation rule UI this way?

[KC Wong]

Before you can quickly switch between audit log and rule details when editing a rule. Precisely what you need when debugging a rule. 

Now both are hidden inside the "..." menu. More clicks required and slower. 

Also the Save and Discard buttons are always displayed at the top and enabled now. The Update button used to be disabled until there's an actual change. 

Before when you make a change and doesn't click Update, you get a warning when you back out of the rule you are editing. Now it just go back without warning you about the unsaved changes. 

[Ajay _view26_]

Hi @KC Wong 

You’re not the only one finding this change frustrating.

That said, I agree it’s a worse debugging flow when you’re switching back and forth constantly between rule details and audit output.

The docs still emphasize that the audit log is the first place to debug a rule, which makes the extra clicks feel even more counterproductive. So I think your criticism is fair: the product is pushing a workflow that the documentation itself says is central to troubleshooting, but the UI now makes that workflow slower

[Bill Sheboy]

Hi @KC Wong 

I agree; the UX changes from a couple of years ago to "hide" the audit log make it more difficult to manage, develop, and debug rules.  One wonders if Atlassian did this to solve the scrolling and state-management problem of the rule being different than what is currently shown in the log...but that was always the case.  For Data Center users, they can still see the old experience with the side-by-side views.

There are many open JAC suggestions to allow seeing the rule and audit log at one time plus better log handling.  Here are some examples if you want to vote for / watch them:

• https://jira.atlassian.com/browse/AUTO-28
• https://jira.atlassian.com/browse/AUTO-36
• https://jira.atlassian.com/browse/AUTO-982
• https://jira.atlassian.com/browse/AUTO-1533

Kind regards,
Bill