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

Wrong address and address level for subject being stored and displayed on DEA #1151

Closed
2 tasks
nupoorkhandelwal opened this issue Oct 24, 2023 · 1 comment
Closed
2 tasks

Comments

@nupoorkhandelwal
Copy link
Collaborator

Describe the bug
In avni-client, a subject registered on address level type A is getting stored in DB on address level type B

To Reproduce
Steps to reproduce the behavior:

  1. Go to DEA ,this is an individual subject whose lowest address for registeration is Village/Hamlet but in DEA and as per DB the address_id corresponds to an AWC which is another address level type and not used in individual registeration anywhere.
  2. DEA link to subject - https://app.avniproject.org/#/app/subject?uuid=b4869afa-7083-4e74-a351-f69ceefbda13
  3. See the address in the DB as well
select * from address_level
left join address_level_type alt on address_level.type_id = alt.id
where address_level.id =334781;
  1. See the screenshots from mobile app which clearly shows the right village address
  2. Attaching other screenshots as well.

Screenshots

Image
Image

Image
Image

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Metabase report to view all other such individuals - https://reporting.avniproject.org/question/2641-apf-individuals-who-are-registered-in-awc-heirarchy

Users dont have a way to fix the data as it is right in mobile app!

Developer Checklist
Developer fixing the bug should fill this checklist.

  • Does the fix require extensive regression testing?
  • Are you mentioning the required scenarios that could be affected?
@nupoorkhandelwal nupoorkhandelwal moved this to New Issues in Avni Product Oct 24, 2023
@mahalakshme mahalakshme moved this from New Issues to In Analysis in Avni Product Oct 24, 2023
@mahalakshme
Copy link
Contributor

according to the reporter, this issue doesn't exist.

@github-project-automation github-project-automation bot moved this from In Analysis to Done in Avni Product Oct 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

3 participants