-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Operations - Routing Rules & Escalation Policies
-
None
-
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
- Incoming Call -> Team -> Schedule -> Escalation -> All 'user' members of the team

- 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
- Remove the user Jira administrator role in the admin panel (https://admin.atlassian.com/);
- Access the Team Members page where you will be able to edit the user role and change it to Admin;
- Grant Jira Administrator role to the user again.