-
Notifications
You must be signed in to change notification settings - Fork 142
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
The same person can be added multiple times as event participant to the same event via the mobile app #12794
Comments
…allowed_to_be_added_as_event_participant
…allowed_to_be_added_as_event_participant
…allowed_to_be_added_as_event_participant
I am reopening the ticket as the behavior described at scenario IV is still reproducible. IV: Via linking an event to a case or contact
Actual behavior: The same person is now listed as event participant to the same event. After sync, this is also visible in the web app once without a resulting case and once with the resulting case. Expected behavior: The person should be listed as an event participant to that event only once, and the case should be linked to that event participant after step 8. |
…allowed_to_be_added_as_event_participant
…_case_with_existent_event_participant #12794 - Link event to case with existent event participant
Verified ticket on the local machine using the latest version of SORMAS from the development branch - 1.94.0-SNAPSHOT(75fa116). |
Bug Description
In the mobile app via the regular create event participant flow, via the mobile app 'line listing' of event participants and via linking events to existing cases and contacts, the same person can be added multiple times as event participant to the same event.
Reproduction Steps
I: Via the regular create event participant flow:
Actual behavior: The same person is now listed twice as event participant to the same event. After sync, this is also visible in the web app.
II: Via the mobile app 'line listing' ('Use rapid event participant entry')
Actual behavior: The same person is now listed as event participant to the same event. After sync, this is also visible in the web app.
III: Via linking an event to a case or contact
Actual behavior: The same person is now listed as event participant to the same event. After sync, this is also visible in the web app.
IV: Via linking an event to a case or contact
Actual behavior: The same person is now listed as event participant to the same event. After sync, this is also visible in the web app.
Expected Behavior
At each of the scenarios, in the moment when the user tries to save an event participant that is for the same person, in the same event, the user should see a pop-up that informs them that the person is already an event participant in the same event, similar to how we have this in the web app.
Active and archived event participants in the same event should be taken into account.
Affected Area(s)
Android app
SORMAS Version
1.92.0, 1.91.0
Android version/Browser
Android Studio
User Role(s)
Default Surveillance Officer
Server URL
local machine
Additional Information
No response
The text was updated successfully, but these errors were encountered: