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

POLIO-1781 Create a "standard chronogram" for all upcoming rounds of a Polio campaign #1949

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

kemar
Copy link
Member

@kemar kemar commented Feb 3, 2025

Create a "standard chronogram" for all upcoming rounds of a Polio campaign.

Related JIRA tickets : POLIO-1781

Changes

This PR:

  • targets only rounds of Polio campaigns
  • and automatically creates a new "standard chronogram":
    1. for all rounds already existing in DB with an upcoming starting date
      • via a data migration
    2. for all future rounds
      • via a new condition in RoundSerializer.create()

How to test

In the IASO UI:

  1. go to Polio > Vaccine module > Chronogram (http://localhost:8081/dashboard/polio/vaccinemodule/chronogram/)
  2. count the number of available Chronograms
  3. go to Polio > Campaigns
  4. choose a campaign of type Polio and add a new round
  5. save changes and keep track of the campaign identifier
  6. go back to Polio > Vaccine module > Chronogram
  7. you should see a new Chronogram for the round you just created

Video

Screen.Recording.2025-02-04.at.15.30.22.mov

@kemar kemar self-assigned this Feb 3, 2025
@kemar kemar force-pushed the POLIO-1781-automatic-creation-of-chronograms branch from 6a1771e to cd57731 Compare February 4, 2025 13:45
@kemar kemar changed the title POLIO-1781 Create a "standard chronogram" for all upcoming rounds of a campaign POLIO-1781 Create a "standard chronogram" for all upcoming rounds of a Polio campaign Feb 4, 2025
@kemar kemar marked this pull request as ready for review February 4, 2025 15:16
@beygorghor beygorghor added the release Should be released in production at next deploy label Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Should be released in production at next deploy
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants