Uploaded image for project: 'Statuspage'
  1. Statuspage
  2. STATUS-270

Do not return component to operational if there is still active PagerDuty incident

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • Apps - Pagerduty
    • None
    • Severity 3 - Minor

      Issue Summary

      Do not return component to operational if there is still active PagerDuty incident

      Steps to Reproduce

      1. Integrate a component on Statuspage with a service on PagerDuty.
      2. Create two incidents on the service we created, with the title "Incident A" and "Incident B."
      3. Resolve the first incident, "Incident A," manually.

      Expected Results

      Component status should still remain in a degraded/outage state.

      Actual Results

      Component is moved back to Operational, despite a service still being impacted in PagerDuty

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Unassigned Unassigned
            photchkiss Parker Hotchkiss
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: