Improve "Some errors" messaging in Automation Audit Log, e.g. during concurrent executions of automation rule

XMLWordPrintable

      Issue summary

      If you have multiple rules that are updating a single issue concurrently it is possible that one of the execution will show a warning like "some errors" even though the trigger worked.

      Steps to reproduce

      1. Create multiple automation rules
      2. Let the rule update the issue at the same time.

      e.g. Editing a custom field with a value.

      Error editing issues
      ABC-123 (We couldn't save your changes. Copy your content, then try reloading the page.)
      

      Expected results

      • If two rules are editing an issue simultaneously, one should wait for the other to finish properly before starting its own editing.

      Actual results

      Edit occurs for one and another edit happens for the other rule. However, the rule fails with a 500/400 error but the edit action is inconsistent. In some cases, it might work and in others, it won't work. Which makes the warning a little bit confusing.

      Extra note

      It would be beneficial if the automation rule stated clearly that "if the edit has actually happened" because although this warning appears, the editing was complete or sometimes it did not complete.

      It seems that the response send back to automation fails with a 500 error and that's what causes the warning to appear as though the issue edit wasn't done in some cases or in others it was done. A better response warning message would help in the audit log to clearly state if the trigger actually failed completely or was successful but with this warning.

       

      ***

       

      Current behavior:

      When an Automation rule is shared between the projects, the log of the rule shows SOME ERRORS according to the failure of the first condition when actually it is successful according to the second one

      This can be confusing for customers.

       

      We should document more clearly in the auditlog message that if a field doesn't exist in a particular project/issue type combination but it's required for a condition check, then we can't assess whether or not the condition should fail or pass.  As such we have to stop the rule execution to avoid false positives or false negatives!

            Assignee:
            Scott Bell
            Reporter:
            Prince N (Inactive)
            Votes:
            30 Vote for this issue
            Watchers:
            22 Start watching this issue

              Created:
              Updated: