Current implementation lists all oncall users, on all escalation levels, for an escalation policy assigned to a specific service. This is how the PagerDuty API works currently.
Problems:
If an escalation policy contains an oncall schedule, then the user currently on-call is returned. But if individual users are used instead all of them are listed.
Same user might exist in different escalation levels which causes the same user to show up multiple times on the list.
The current implementation doesn't use the gravatar image used in PagerDuty. It uses a dummy avatar icon for everyone.
Proposed implementation:
List only users in escalation level 1 - these are the users that are actually oncall.
Remove duplicate users from the oncall user list
Add support for user profile picture and fallback to dummy avatar icon when an image is not provided.
Issue number: #36
Type of change
[ ] New feature (non-breaking change which adds functionality)
[x] Fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Description
Current implementation lists all oncall users, on all escalation levels, for an escalation policy assigned to a specific service. This is how the PagerDuty API works currently.
Problems:
Proposed implementation:
Issue number: #36
Type of change
Checklist
If this is a breaking change 👇
Acknowledgement
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.