Skip to content

MedEvac: Common Services user filter + distribution list alongside separate email - #1262

Open
morgang-adappt wants to merge 4 commits into
medevac/email-schedulerfrom
medevac/cs-user-filter
Open

MedEvac: Common Services user filter + distribution list alongside separate email#1262
morgang-adappt wants to merge 4 commits into
medevac/email-schedulerfrom
medevac/cs-user-filter

Conversation

@morgang-adappt

@morgang-adappt morgang-adappt commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Description

Adds two fields to email notification datasets. csFilter holds a filter descriptor used to select recipients from the Common Services user directory, and individualEmailToDistributionList lets a send-separate dataset also be delivered to the notification's distribution list. Both are plumbed through the Mongoose model, GraphQL input and GraphQL type.

Validation on addEmailNotification / editEmailNotification is rewritten so a send-separate notification can be saved without a distribution list, while still requiring at least one recipient source overall. This replaces the previous check, which incorrectly passed notifications that had no recipients at all.

Useful links

Type of change

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

  • Test A
  • Test B

Screenshots

Please include screenshots of this change. If this issue is only back-end related, and does not involve any visual change of the platform, you can skip this part.

Checklist:

( * == Mandatory )

  • * I have set myself as assignee of the pull request
  • * My code follows the style guidelines of this project
  • * Linting does not generate new warnings
  • * I have performed a self-review of my own code
  • * I have put the ticket for review, adding the oort-backend team to the list of reviewers
  • * I have commented my code, particularly in hard-to-understand areas
  • * I have put JSDoc comment in all required places
  • * My changes generate no new warnings
  • * I have included screenshots describing my changes if relevant
  • * I have selected labels in the Pull Request, according to the changes with code brings
  • I have made corresponding changes to the documentation ( if required )
  • I have added tests that prove my fix is effective or that my feature works
  • * New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

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.

2 participants