onaio
EUSM: Users unassigned from active missions
Currently users are assigned to missions that have expiry dates. When a mission expires, the users are assigned from the mission and its status changes from active to completed.
Bug
Currently, on production, users seem to be unassigned from missions that have expiry dates of 1st and 2nd February even though the mission is still active. - see the screenshot of the active missions:
See a mission that is still active and the team has been unassigned.
Ask
- Investigate why this is happening. Question: Is there a way to know whether someone unassigned the teams and it's not a system error?
@AnnieMungai from web; we cannot tell if this was due to a user action or due to a system error, on the server side we could maybe check api logs and see if there was a request made that could have affected the assignments for the above plan 6b6ab6c9-7ad7-59d7-80e2-893e1c2058cc.
Peculiarly when I checked assignments done for the plan, I noticed, the to_date is set to 2024-02-01 but the duration end date is a day after [2024-01-23,2024-02-02).
This explains why the assignments do not show up since the to_date is <= to today. If server side thinks that duration and to_date can differ as shown above, it might imply that the team assignment were revoked from fhir-web, or any other http client like postman.
We had a similar problem in WHO-ANC Indonesia due a difference in the linux server timezone and that of the postgres database. I have checked these timezones and they are the same.
