Issue Summary

In some cases, Automation for Jira (A4J) may fail to display an error message while publishing (saving/updating) a rule. This will cause the spinner (throbber) to display indefinitely, providing no indication that the save has failed or why.

As a result, users are left confused about why Jira can't save an automation rule since the page appears frozen.

Steps to Reproduce

Several server-side rule validation errors can cause this bug. As an example:

1. Authenticate as a user with project admin access but not global Jira admin access.
2. Navigate to project > Project settings > Automation.
3. Create a test rule rule and remain on the rule config page.
4. Duplicate that page in another tab.
5. Delete the rule in the first tab.
6. Without refreshing, attempt to delete the rule again in the second tab.

Expected Results

The spinner disappears, and a descriptive error message ("The rule appears to have been deleted. Please reload and try again.") is displayed. Display a generic error message if the server didn't provide a specific reason.

Actual Results

Nothing. The loading icon appears indefinitely until the user navigates away.

Workaround

Review the response code and body in the HAR file data. This can be accessed from the web browser's developer tools networking tab. The request will be a failed (non-2XX) POST or PUT to /rest/cb-automation/latest/project/<projectId-or-GLOBAL>/rule/<rule-id>.

After identifying and correcting the problem, reload the page and re-attempt to publish the rule.