Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On call engineers are duplicated #36

Closed
jcoelho93 opened this issue Nov 8, 2023 · 3 comments
Closed

On call engineers are duplicated #36

jcoelho93 opened this issue Nov 8, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@jcoelho93
Copy link

jcoelho93 commented Nov 8, 2023

Describe the bug

There are 2 issues with the list of on call engineers:

  • It does not identify which engineer is the primary on call responder
  • There are duplicate engineers in the list

To Reproduce
Steps to reproduce the behavior:

  1. Go to a service's page, with an escalation policy with multiple engineers
  2. The list of on call engineers will not display the primary on call
  3. The list of on call engineers will have some duplicates

Expected behavior

  • The primary on call engineer should be clearly identified.
  • There shouldn't be duplicates, if there are then it should be easy to understand why there are duplicates

Screenshots

  • David Wallace is the primary on call engineer, but it's not identified as so.
  • David Wallace and Jim Halpert are duplicated for some reason
Screenshot 2023-11-08 at 13 27 38

Desktop (please complete the following information):

  • OS: MacOS
  • Browser chrome
  • Version 119
@jcoelho93 jcoelho93 added the bug Something isn't working label Nov 8, 2023
@t1agob t1agob self-assigned this Nov 8, 2023
@t1agob
Copy link
Contributor

t1agob commented Nov 9, 2023

Hi @jcoelho93!
I was able to replicate the issue if I specify users individually or have multiple levels in the escalation policy. If I use a on-call schedule instead with just one level I only get the user currently on-call.

Can you please confirm that your use case fits into the first scenario? Thanks!

@jcoelho93
Copy link
Author

@t1agob yes, I confirm, we have an escalation policy with multiple levels.

@t1agob
Copy link
Contributor

t1agob commented Nov 15, 2023

@jcoelho93 this issue has now been resolved and merged into next branch (#38) . It will be merged into main and released by the end of the week November 17.

I have solved the issues you reported and now the plugin only lists oncall users on escalation level 1 and no duplicates will show up. I have also added support for user's profile picture instead of the default dummy avatar icon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants