-
Notifications
You must be signed in to change notification settings - Fork 6
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
POLIO-1762 POLIO-1764 POLIO-1765: Campaign combination cVDPV1 & cVDPV2 w/ 2 vaccines nOPV2 & bOPV #1876
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The global feature still needs some spec and this PR will have to be released together with changes in the vaccine module, so I tagged is as DO NOT MERGE in the meantime.
About the feature itself:
Nothing shocking in the code
- The hashed colors don't appear on the calendar
Screen.Recording.2024-12-18.at.12.08.43.mov
- They don't appear in the xlsx export of the calendar either:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️
{ | ||
label: 'nOPV2 & bOPV', | ||
value: 'nOPV2 & bOPV', | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not correct: supplychain will still handle the vaccines separately. I'll open a separate ticket for that as it will require some backend as well I think
|
- On Round and Campaign - Includes subactivities scopes
- show individual vaccines for bOPV & nOPV2 campaigns - Include subactivities vaccines
…opv_nopv_new_vaccine POLIO-1803: adapt supplychain to bopv/nopv new vaccine
We will have to create a new Virus Type: cVDPV1 & cVDPV2 with the Vaccine Type: nOPV2 & bOPV associated
Related JIRA tickets POLIO-1762
Self proofreading checklist
Changes
How to test
If a specific config is required explain it here: dataset, account, profile, etc.
Print screen / video
Follow the Conventional Commits specification
The merge message of a pull request must follow the Conventional Commits specification.
This convention helps to automatically generate release notes.
Use lowercase for consistency.
Example:
Note that the Jira reference is preceded by a line break.
Both the line break and the Jira reference are entered in the Add an optional extended description… field.