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

Deleting an immunization program master list in OG is not reflected in OMS #6896

Open
adamdewey opened this issue Mar 11, 2025 · 2 comments
Open
Labels
feature: GAPS Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release
Milestone

Comments

@adamdewey
Copy link
Contributor

adamdewey commented Mar 11, 2025

What went wrong? 😲

If an immunization program master list is deleted in OG it still appears in Programs > Immunizations in OMS

Image

Image

Expected behaviour 🤔

Master lists deleted in OG should not be shown in the UI in OMS

Quote: "Chris sez we probably ain't filtering soft deleted program table records, or we're forgetting to soft delete them as an effect of soft deleting a master list"

How to Reproduce 🔨

Steps to reproduce the behaviour:

  1. Create an immunization program master list in OG
  2. Observer the immunization program appear in OMS
  3. Delete the master list in OG
  4. Observer the immunization program remains in OMS

Your environment 🌱

  • Open mSupply Version: 2.6.00
  • Legacy mSupply Central Server Version: 8.00.17
@adamdewey adamdewey added needs daily triage New bug to be triaged by the release team needs triage labels Mar 11, 2025
@jmbrunskill jmbrunskill added Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release and removed needs daily triage New bug to be triaged by the release team labels Mar 12, 2025
@jmbrunskill
Copy link
Contributor

Daily Triage note: If we need it for a client urgently could probably go into 2.6? But would prefer 2.7 otherwise as 2.6 has already grown a lot and hard for testers & devs if we keep adding to the release

@adamdewey
Copy link
Contributor Author

Don't think urgent, 2.7 or beyond would be fine

@andreievg andreievg added this to the v2.7.0 milestone Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: GAPS Severity: High Bugs breaking core functionality or with no/unacceptable workaround. High impact. Next patch release
Projects
None yet
Development

No branches or pull requests

3 participants