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

Local Body required but unavailable for some selected districts #8819

Closed
AdityaJ2305 opened this issue Oct 17, 2024 · 2 comments
Closed

Local Body required but unavailable for some selected districts #8819

AdityaJ2305 opened this issue Oct 17, 2024 · 2 comments

Comments

@AdityaJ2305
Copy link
Contributor

AdityaJ2305 commented Oct 17, 2024

Describe the bug
While creating a Patient, many districts lack local body options, but the field is still required, blocking form submission. This affects multiple districts across states, making it impossible to proceed without selecting an unavailable option.

To Reproduce
Steps to reproduce the behavior:

  1. Navigate to the Patient Tab.
  2. Click on Add Patient Details.
  3. Choose any option under the Facility field.
  4. Scroll to the State field.
  5. Select a State and a District where no local body options are available.
  6. Attempt to submit the form.
  7. Observe the error.

Expected behavior
The form should allow submission when no local body options are available for the selected district, but require it for districts where options are available .

Screenshots

Image

Additional context
Hey @Nihal @rithviknishad, could you please confirm if this is a valid issue? If so, I’d be happy to work on it.

@aparnacoronasafe
Copy link
Member

@AdityaJ2305 you have found a valid bug.

We already have local bodies list for all states/districts. They may not be enabled in all instances.

The solution should be to enable the list for all states.

The field will always stay mandatory

@AdityaJ2305
Copy link
Contributor Author

@aparnacoronasafe, it seems this issue is a backend problem. The frontend is functioning correctly, so we can close this issue here.

@bodhish bodhish closed this as not planned Won't fix, can't repro, duplicate, stale Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants