Cause of this bug:additionalEntries are responsible for including participants outside of HAs region in the reports; this can happen due to RoS site change, for example
The issue was that it only included entries with status = 'assigned-new-site' - this status is valid when assigning a new site as HA; yet when MoH makes an edit, this status is not being assigned
Proposed fix:
Include all edited entries in the report, if they apply to the same health region as HA at any point.
This can be done y identifying updated entries: 'data.user <>': 'NULL' and checking if HA is allowed to see them based on region
What else included?
Splitting getRosReport into getMohRosMilestonesReport and getHARosMilestonesReport
https://freshworks.atlassian.net/browse/HCAP-1319
Cause of this bug:
additionalEntries
are responsible for including participants outside of HAs region in the reports; this can happen due to RoS site change, for example The issue was that it only included entries withstatus = 'assigned-new-site'
- this status is valid when assigning a new site as HA; yet when MoH makes an edit, this status is not being assignedProposed fix: Include all edited entries in the report, if they apply to the same health region as HA at any point. This can be done y identifying updated entries:
'data.user <>': 'NULL'
and checking if HA is allowed to see them based on regionWhat else included? Splitting
getRosReport
intogetMohRosMilestonesReport
andgetHARosMilestonesReport