Skip to content
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

Resources API is not filtering by Patient in Patient Details Page and Status in Resource Board #10149

Closed
nihal467 opened this issue Jan 24, 2025 · 6 comments · Fixed by ohcnetwork/care#2799
Assignees
Labels
P1 breaking issue or vital feature

Comments

@nihal467
Copy link
Member

nihal467 commented Jan 24, 2025

Describe the bug

On the Patient Details page, the resources are not being filtered based on the assigned patient. Additionally, the status filter in the Resource Board is not functioning correctly, causing all resource requests to be displayed across all sections

Steps to Reproduce:

  1. Go to the 'Patient Details' page.
  2. Create a new patient.
  3. Scroll down to the 'Requests' section of the patient details page.
  4. Observe that four unwanted requests are automatically generated.

Expected behavior

  1. Resources should be filtered based on the specific patients in the "Resources" section of the patient details page
  2. Resource requests should be displayed under their respective status headings in the Resource Board

Screenshots

Image
![Image](https://github.com/user-attachments/assets/135e4b2c-fdec-4c4d-90e8-e408d7f7d23

@AdityaJ2305
Copy link
Contributor

Hey @nihal467 , I wanted to work on this issue

@Mahendar0701
Copy link
Contributor

Mahendar0701 commented Jan 24, 2025

It is happening for all patients not only for new patients.

I think this is backend issue because backend is sending all the requests in response for every patient

@AdityaJ2305
Copy link
Contributor

It is happening for all patients not only for new patients.

I think this is backend issue because backend is sending all the requests in response for every patient

Yes

cc: @nihal467

@nihal467 nihal467 changed the title Four unwanted Request are generated for every new patient created Resources Not Filtered by Patient in Patient Details Page and Status Filter Not Working in Resource Board Jan 24, 2025
@nihal467
Copy link
Member Author

nihal467 commented Jan 24, 2025

@rithviknishad have already worked on it, so assigning it to him

@nihal467 nihal467 added the P1 breaking issue or vital feature label Jan 24, 2025
Copy link

⚠️ Refrain from assigning this issue to yourself if you have another P1 issue assigned that is not yet closed.
@rithviknishad kindly acknowledge this message by commenting 'Acknowledged' below.

@nihal467 nihal467 changed the title Resources Not Filtered by Patient in Patient Details Page and Status Filter Not Working in Resource Board Resources API is not Filtering by Patient in Patient Details Page and Status Filter Not Working in Resource Board Jan 25, 2025
@nihal467 nihal467 changed the title Resources API is not Filtering by Patient in Patient Details Page and Status Filter Not Working in Resource Board Resources API is not Filtering by Patient in Patient Details Page and Status Not Working in Resource Board Jan 25, 2025
@nihal467 nihal467 changed the title Resources API is not Filtering by Patient in Patient Details Page and Status Not Working in Resource Board Resources API is not filtering by Patient in Patient Details Page and Status in Resource Board Jan 25, 2025
@Jacobjeevan Jacobjeevan marked this as a duplicate of #10208 Jan 27, 2025
@Sulochan-khadka
Copy link
Contributor

It is P1, still not merged? Can i be of any help to get this merged as soon as possible? @nihal467

@github-actions github-actions bot added needs-triage question Further information is requested labels Jan 29, 2025
@nihal467 nihal467 added this to the Stable Staging Release milestone Jan 30, 2025
@Jacobjeevan Jacobjeevan removed question Further information is requested needs-triage labels Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 breaking issue or vital feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants