-
Notifications
You must be signed in to change notification settings - Fork 519
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
Multi selection of investigations not working in Patient log lab results #9144
Comments
(1) Should be able to select multiple investigations |
when user selects one investigation group like 'Biochemistry Test', it shows all tests under 'Biochemistry Test', next if user selects 'FBS' which comes under 'Biochemistry Test', what should be the expected behavior, only one 'FBS' should be shown or all the tests of 'Biochemistry Test' should be shown, since user has selected 'Biochemistry Test' before. |
@nihal467 @Jacobjeevan I Would like to work on this issue. Would you assign to me? |
@nihal467 Yes . I Would like to work on this issue |
@rohitlingarker are you working on this issue |
@rohitlingarker unassigning you due to inactivity and assign it to @Jeffrin2005 |
Describe the bug
When Logging the lab results in the Patient investigation tab, we cannot select multiple investigations at once. Atmost we can select 2 (that is by double clicking one option and then clicking on second one, this may also be a bug).
When selecting multiple investigations from the dropdown in the multiselect form for uploading lab results, the input form for previously selected investigations gets hidden. However, if those forms were filled, their data is still processed during form submission, and empty form also getting submitted.
To Reproduce
Steps to reproduce the behavior:
Log Lab Results
Screenshots
If applicable, add screenshots to help explain your problem.
https://github.com/user-attachments/assets/8e586585-9382-459f-a262-efc2734656bd
Desktop (please complete the following information):
Additional context
I would like to be assigned to this issue and requesting for expected behaviour
The text was updated successfully, but these errors were encountered: