SLA breach events causes looping triggers of automation rules

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • Component/s: SLA
    • None
    • 3
    • Severity 2 - Major

      Issue Summary

      SLA events that trigger notifications or other events in Jira Service Desk automation may start looping.

      Steps to Reproduce

      _This is an intermittent issue and not reliably reproducible _

      1. Create Jira Service Desk project
      2. Create an SLA rule and goal in the JSD project
      3. Create an automation rule that triggers on an SLA breaching event.

      Expected Results

      When the SLA breach the rule is triggered once.

      Actual Results

      When the SLA is breached multiple breach events are fired by Rolex causing the automation rule to trigger multiple times.

      Workaround

      Currently, it seems that making a change to the automation rule which is looping, saving this change will stop the looping.
      After the change is made and looping has stopped the change can be reverted.

      If this does not work or you are finding consistent issues with this happening please contact Atlassian Support.

              Assignee:
              Unassigned
              Reporter:
              Battlebeard (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: