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

fix(oncall-api): return all users from lowest escalation level #33

Merged
merged 6 commits into from
Mar 1, 2024

Conversation

brianphillips
Copy link
Contributor

@brianphillips brianphillips commented Feb 23, 2024

Description

Instead of return all users that match the escalation level of the first user returned in the oncall list, return users that match the lowest escalation level.
Previously, if a higher escalation level user was the first item in the array, only users at that same level would be returned.

Issue number: Fixes #34

Type of change

  • New feature (non-breaking change which adds functionality)
  • Fix (non-breaking change which fixes an issue)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

  • I have performed a self-review of this change
  • Changes have been tested
  • Changes are documented
  • Changes generate no new warnings
  • PR title follows conventional commit semantics

If this is a breaking change 👇

  • I have documented the migration process
  • I have implemented necessary warnings (if it can live side by side)

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.

t1agob and others added 6 commits February 12, 2024 12:18
Bumps [ip](https://github.com/indutny/node-ip) from 2.0.0 to 2.0.1.
- [Commits](indutny/node-ip@v2.0.0...v2.0.1)

---
updated-dependencies:
- dependency-name: ip
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
…n/ip-2.0.1

build(deps): Bump ip from 2.0.0 to 2.0.1
Instead of return all users that match the escalation level of the first user returned in the oncall list, return users that match the lowest escalation level.
Previously, if a higher escalation level user was the first item in the array, only users at that same level would be returned.

Fixes PagerDuty/backstage-plugin#77
@brianphillips
Copy link
Contributor Author

@t1agob could you take a look at this please?

@t1agob t1agob changed the base branch from main to next March 1, 2024 00:15
@t1agob
Copy link
Collaborator

t1agob commented Mar 1, 2024

Hi @brianphillips.
Thanks for submitting this PR. I have tested it and it doesn't change the overall behaviour of the API and fixes the issue of not showing the ordered items.

Approved! I have changed the base branch to comply with our guidelines. I'll work on merging this to main and release a new version shortly.

@t1agob t1agob merged commit 495e7c3 into PagerDuty:next Mar 1, 2024
1 check passed
@brianphillips brianphillips deleted the fix-oncall-api-users branch March 1, 2024 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

On-call shows individual that is N levels down from the first level of the escalation policy
2 participants