oncall-engine/engine/apps/google
Joey Orlando 3f24bfce95
Google Calendar Integration - consider current oncall shifts for autogeneration of shift swap requests (#4160)
# What this PR does

Fixes issue where you create a Google Calendar OOO that overlaps with an
in-progress oncall shift (currently we only consider future/upcoming
shifts).

Related to https://github.com/grafana/oncall-private/issues/2555

## Checklist

- [x] Unit, integration, and e2e (if applicable) tests updated
- [x] Documentation added (or `pr:no public docs` PR label added if not
required)
- [x] Added the relevant release notes label (see labels prefixed w/
`release:`). These labels dictate how your PR will
    show up in the autogenerated release notes.
2024-04-05 13:15:05 +00:00
..
migrations Google OAuth2 flow + fetch Google Calendar OOO events (#4067) 2024-04-02 14:59:03 -04:00
models Google Calendar Out of Office events - autogenerated shift swap requests (#4104) 2024-04-02 20:10:16 +00:00
tests Google Calendar Integration - consider current oncall shifts for autogeneration of shift swap requests (#4160) 2024-04-05 13:15:05 +00:00
__init__.py Google OAuth2 flow + fetch Google Calendar OOO events (#4067) 2024-04-02 14:59:03 -04:00
client.py Google Calendar Out of Office events - autogenerated shift swap requests (#4104) 2024-04-02 20:10:16 +00:00
constants.py Google Calendar Out of Office events - autogenerated shift swap requests (#4104) 2024-04-02 20:10:16 +00:00
tasks.py Google Calendar Integration - consider current oncall shifts for autogeneration of shift swap requests (#4160) 2024-04-05 13:15:05 +00:00
types.py Google Calendar Out of Office events - autogenerated shift swap requests (#4104) 2024-04-02 20:10:16 +00:00
utils.py Google Calendar Out of Office events - autogenerated shift swap requests (#4104) 2024-04-02 20:10:16 +00:00