Incoming Call is routed through an Escalation policy intended exclusively for 'User' team-role members, it incorrectly also notifies a team member with the 'Admin' role.

XMLWordPrintable

    • 2
    • Severity 3 - Minor

      Issue Summary

      When the Incoming Call is routed to an Escalation policy which is meant to call only 'User' team-role members of the Team, it also calls a user which has the 'Admin' team-role.

      Steps to Reproduce

      1. Incoming Call -> Team -> Schedule -> Escalation -> All 'user' members of the team 
      2. User is global admin and in Team's configuration Member page user showed as admin in JSM because of global admin role.

      Expected Results

      Escalation policy which is meant to call only 'User' team-role members of the Team

      Actual Results

      Escalation policy which is meant to call only 'User' team-role members of the Team, it also calls a user which has the 'Admin' team-role.The user is not actually not a team admin. We are showing user as admin in JSM because of global admin role.

      Workaround

      1. Remove the user Jira administrator role in the admin panel (https://admin.atlassian.com/);
      2. Access the Team Members page where you will be able to edit the user role and change it to Admin;
      3. Grant Jira Administrator role to the user again.

            Assignee:
            Unassigned
            Reporter:
            Saama Tabassum
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: