Skip to content

Mini project#215

Open
Speedtrain49 wants to merge 2 commits intoramfam101:developfrom
Speedtrain49:Mini-Project
Open

Mini project#215
Speedtrain49 wants to merge 2 commits intoramfam101:developfrom
Speedtrain49:Mini-Project

Conversation

@Speedtrain49
Copy link
Copy Markdown

(Please remove this line only before submitting your PR. Ensure that all relevant items are checked before submission.)

Describe your changes

Added an escalation feature to allow for email notifications when escalation happens

Write your issue number after "Fixes "

Fixes #123

Please ensure all items are checked off before requesting a review. "Checked off" means you need to add an "x" character between brackets so they turn into checkmarks.

  • [Y ] (Do not skip this or your PR will be closed) I deployed the application locally.
  • [Y ] (Do not skip this or your PR will be closed) I have performed a self-review and testing of my code.
  • [Y ] I have included the issue # in the PR.
  • [ ]Y I have added i18n support to visible strings (instead of <div>Add</div>, use):
const { t } = useTranslation();
<div>{t('add')}</div>
  • [ Y ] I have not included any files that are not related to my pull request, including package-lock and package-json if dependencies have not changed
  • [ Y ] I didn't use any hardcoded values (otherwise it will not scale, and will make it difficult to maintain consistency across the application).
  • [Y ] I made sure font sizes, color choices etc are all referenced from the theme. I don't have any hardcoded dimensions.
  • [Y ] My PR is granular and targeted to one specific feature.
  • [Y ] I ran npm run format in server and client directories, which automatically formats your code.
  • [ Y ] I took a screenshot or a video and attached to this PR if there is a UI change.
Screenshot 2026-04-08 221538 Screenshot 2026-04-08 221538

Introduce escalation support for monitors and incidents across client and server.

- Client: add EscalationSettings component, integrate escalation fields into CreateMonitor form, update monitor types and validation, and i18n strings.
- Server: extend Monitor and Incident models/types with escalation fields, add migration to populate defaults, expose PATCH /monitors/:monitorId/escalation, and add request validation.
- Business logic: implement EscalationService to detect and trigger escalations, wire it into the SuperSimpleQueue (scheduled check every 5 mins), and reset escalation state when incidents resolve.
- Repositories/controllers: add active incident query, repository mapping for new fields, and controller handler to validate and persist escalation settings.

Notes: notifications sending is stubbed in the service (marked as TODO); migration adds default values for existing documents. Unit/integration tests may be needed for the new flow.
-There was a bug with the saving of escalation settings.
-It was handled...
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.

1 participant