You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One more issue is observed - On trying to turn on the toggle of facility-facility group association from facility details page, the API responds with 200 status code but the toggle is turned on. It don't get changed even after refreshing the URL. May be this there is some limitation set for association. Need to address the issue also. https://jam.dev/c/35b28a39-1567-4403-bfeb-fd55dfdd3360
Current behavior
If more than 10 facility groups are linked to a facility, only the first 10 are displayed in the "Linked Groups" section of the facility details page. Groups beyond the 10th are not visible.
The "Add Group" modal only displays up to 50 groups.
If there are more than 50 groups in the system, the 51st group or beyond does not appear in the modal, even when searched by name.
A maximum of 12 facility groups can be linked to a facility.
If a user tries to add a 13th group:
The group does not appear as checked in the modal upon reopening.
This allows the user to repeatedly add the same group, resulting in duplicate visibility of the same facility group in the "Linked Facilities" section.
Expected behavior
The "Linked Groups" section should display all linked facility groups, regardless of the count.
The "Add Group" modal should show all available groups without limitation or at least provide a warning when the limit is reached.
Linked groups should persist correctly, and once a group is checked and saved, it should remain checked when the modal is reopened.
Steps to reproduce the issue
Link more than 10 facility groups with a facility.
Open the facility details page and note that only 10 groups are visible.
Open the "Add Group" modal and try to add a 51st group, ensuring it doesn’t appear in the modal even after searching.
Attempt to check and save a 13th group and observe that it does not remain checked upon reopening the modal.
Note
One more issue is observed - On trying to turn on the toggle of facility-facility group association from facility details page, the API responds with 200 status code but the toggle is turned on. It don't get changed even after refreshing the URL. May be this there is some limitation set for association. Need to address the issue also.
https://jam.dev/c/35b28a39-1567-4403-bfeb-fd55dfdd3360
Current behavior
If more than 10 facility groups are linked to a facility, only the first 10 are displayed in the "Linked Groups" section of the facility details page. Groups beyond the 10th are not visible.
The "Add Group" modal only displays up to 50 groups.
If there are more than 50 groups in the system, the 51st group or beyond does not appear in the modal, even when searched by name.
A maximum of 12 facility groups can be linked to a facility.
If a user tries to add a 13th group:
The group does not appear as checked in the modal upon reopening.
This allows the user to repeatedly add the same group, resulting in duplicate visibility of the same facility group in the "Linked Facilities" section.
Expected behavior
The "Linked Groups" section should display all linked facility groups, regardless of the count.
The "Add Group" modal should show all available groups without limitation or at least provide a warning when the limit is reached.
Linked groups should persist correctly, and once a group is checked and saved, it should remain checked when the modal is reopened.
Steps to reproduce the issue
Link more than 10 facility groups with a facility.
Open the facility details page and note that only 10 groups are visible.
Open the "Add Group" modal and try to add a 51st group, ensuring it doesn’t appear in the modal even after searching.
Attempt to check and save a 13th group and observe that it does not remain checked upon reopening the modal.
Environment details
App version : v1.9.3
App environment : UAT
Additional information
https://jam.dev/c/def1e8f0-d7f0-429f-bbc9-6d703a6f5237
The text was updated successfully, but these errors were encountered: