Issue Summary

      When configuring outgoing rules for "Create Statuspage incidents for Jira Service Management alerts," the actions associated with the rules "If alert is escalated to next responder" and "If user escalates the alert" are swapped. This misconfiguration causes the incorrect rule to be executed when an alert is escalated.

      Steps to Reproduce

      1. Configure Jira Service Management to integrate with Statuspage for creating incidents based on alerts.
      1. Set up outgoing rules with the following configurations:
        • Rule A: "If alert is escalated to next responder"
        • Rule B: "If user escalates the alert"
      1. Trigger an alert escalation to the next responder in JSM and observe the effect on Statuspage.
      1. Similarly, manually escalate a user alert in JSM and observe the effect on Statuspage.

      Expected Results

      • For the rule "If alert is escalated to next responder," Statuspage should create an incident when the alert is automatically escalated to the next responder.
      • For the rule "If user escalates the alert," Statuspage should create an incident when a user manually escalates the alert.

      Actual Results

      • When the rule "If alert is escalated to next responder" is triggered, the action configured for "If user escalates the alert" is executed instead.
      • When the rule "If user escalates the alert" is triggered, the action configured for "If alert is escalated to next responder" is executed instead.

      Workaround

      Currently there is no known workaround for this behavior. Need to use the oppsite name if this requires to be implemented. Means for the rule "If alert is escalated to next responder" is required, then use "If user escalates the alert"

            [JSDCLOUD-16027] Swapped Actions in JSM-Statuspage integration outgoing rules

            There are no comments yet on this issue.

              Unassigned Unassigned
              f04db879384a Mubeen Mohammed
              Affected customers:
              1 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated: