Migrated "Global Operations Admin" not accepted as "Admin" by default on Escalation/Notification Policies

XMLWordPrintable

    • 2
    • Severity 3 - Minor

      Issue Summary

      Migrated "Global Operations Admin" not accepted as "Admin" by default on Escalation/Notification Policies so notifications are not triggered.

      Steps to Reproduce

      1. Need to confirm that previous "Owner" user was migrated as "Global Operations Admin" in JSM Operations
      2. Add the "Notify Admin members of a team" escalation/notification rule
      3. Trigger the escalation/notification on any alert

      Expected Results

      Global Operations Admin should be notified as part of the Escalation/Notification rule

      Actual Results

      User didn't get notified because in backend, it is not an "Admin"

      Workaround

      Try removing the Global Ops / Jira admin role of the affected users, manually setting their team member roles to ADMIN, and finally changing their global role back to ADMIN should force the stored team member role to be admin. 

              Assignee:
              Unassigned
              Reporter:
              Ignacio Huerta
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: