opensrp / opensrp-client-chw

Reference OpenSRP application for Community Health Workers (CHWs)
Other
3 stars 21 forks source link

CRVS: Change Requests/QA Feedback Issues #1983

Closed ageryck closed 2 years ago

ageryck commented 2 years ago

This will be a holder issue for bug reproduced and suggested changes, each task resolved or assigned to an engineer will be marked as done;

joyce-x-chen commented 2 years ago

NOTES @ageryck The Remove Member Form (Died) tab in the data dictionary was locked so I created a duplicate called Copy of Remove Member Form (Died) tab and suggested edits with red text.

GENERAL FEEDBACK FOR CLEANING UP THE DATA DICTIONARY

SPECIFIC FEEDBACK FOR DEATH REPORTING

  1. Using demo4/Amani124
  2. Select Esco family, which only has one Male 63-year-old family member - Julian Esco
  3. Select Julian Esco, 63
  4. Click 3 dots in upper right-hand corner and select "Remove this person"
  5. Here, an error message pops up stating "Before you remove this member you must select a new family head." However, since this person lives alone this is not possible and you cannot report his death.

Preferably, if a family only has one person, the error message would state: "This family only has one member. Please confirm if you would like to remove the entire family." Then a button that takes you to "Remove family" page.

SPECIFIC FEEDBACK FOR BIRTH REPORTING

joyce-x-chen commented 2 years ago

Please remove the Liberia logo from the CRVS login page.

ageryck commented 2 years ago

Please remove the Liberia logo from the CRVS login page.

We will replace this with DRC logo for the current CFC App, client did not share any specific app branding

rowo commented 2 years ago

@ageryck @joyce-x-chen just reviewed the app from https://onaio.slack.com/archives/C01KKF9LUR1/p1643981557660599 and read the thread above (tried not to reproduce the known issues).

  1. We definitely cannot assume reason for removal is always death — if only to account for user error.
  2. The relevancy logic is not working in the "remove family member (over 5)" form. Nothing should appear before a reason for removal is selected as defined in the "Relevance" column. I'm sure this was mentioned and i missed it.. It works for under 5.
  3. Re: the above comment, The Remove family form currently only gives 2 options: "Moved away" and "Other." This form should look the same as the Remove family member form. The "Remove family" and "Remove family member" forms cannot be the same since the fields aren't the same and we don't really want the remove family to be like a bulk death reporting form either. The workflow for removing the last remaining person would probably be doing the "remove family member form" with a confirmation in step one that you are removing the last person, which will delete the family/structure as well. If you are trying to remove the entire family and want to say they all died, I feel like you'd have to report each one died first, then remove the family.
  4. I updated a check item on the above comment to properly display the checkbox. This was the comment for I don't see "Certificate received" and "Certificate not received" statuses displaying in the Out of area death page. which I am also seeing.
  5. What is the sorting for birth and death cert register lists?

I also noticed some statuses not updating/saving. If we can prioritize those... they are probably the main issue to figure out before UAT. If you are having trouble replicating @ageryck maybe we should have a meeting to identify the broken things vs. stuff we can live with.

joyce-x-chen commented 2 years ago

@rowo good point about not using remove entire family to register the death of a person who lives alone. I proposed that as a workaround to the logic that prevents one from using the remove family member without re-assigning head of household. In this case, we cannot register the death of an individual who lives alone. Is it necessary to keep the logic that prevents the removal of a family member without re-assigning head of household? cc: @ageryck

joyce-x-chen commented 2 years ago

@ageryck Leigh and I have noticed while testing the CRVS app that we periodically get logged out of the app and receive the following error message: “you have been logged off as your account has been disabled.” In this Slack thread, we received a few suggestions:

This is a nice to have - if there isn't time to squeeze this in, that's ok.

ageryck commented 2 years ago

@rowo good point about not using remove entire family to register the death of a person who lives alone. I proposed that as a workaround to the logic that prevents one from using the remove family member without re-assigning head of household. In this case, we cannot register the death of an individual who lives alone. Is it necessary to keep the logic that prevents the removal of a family member without re-assigning head of household? cc: @ageryck

looking into this

ageryck commented 2 years ago

@ageryck Leigh and I have noticed while testing the CRVS app that we periodically get logged out of the app and receive the following error message: “you have been logged off as your account has been disabled.” In this Slack thread, we received a few suggestions:

  • [ ] Increase the time before a user is automatically logged out, and it should be following a period of inactivity.
  • [ ] Display a different error message such as "You have been logged out due to inactivity. Please log in again."

This is a nice to have - if there isn't time to squeeze this in, that's ok.

@allan-on will be looking on this logged under this issue

ageryck commented 2 years ago

majority of listed issues have been translated into tshirt size issue and already handled pending QA on the project board, closing this while parking the entire family removal issue for future handling

charlene-570 commented 2 years ago

From @joyce-x-chen here are the bug reports:

1.Relevance and select one options should be specified in the relevant columns in the data dictionary, not written in the label columns and displayed to the CHW. Can we please clean this up? For example [ ] We don't need to display "(Y/N)" to the CHW. "Yes" and "No" will appear in the drop down list

QA Results Actual Results: "(Y/N)" is still displayed see screenshot below Screenshot_20220210-171404

Expected Results: "(Y/N)" should not be displayed

[] We don't need to display "(if death notification done)" to the CHW. We should just note the relevance {death notification}="Yes" for programming the workflow

QA results:

Death notification is displayed see screenshot below Screenshot_20220210-173032

Expected results:

Death notification done should not be displayed only note the relevance {death notification}="Yes" for programming the workflow

From issue "Please remove the Liberia logo from the CRVS login page" Logo has been changed From Liberia to “Justice Paix Travail” See screenshot below ! Screenshot_20220214-141410

charlene-570 commented 2 years ago

@ageryck Report on the following : The Relationship descendant drop down Sibling is shown twice see screenshot below Screenshot_20220215-142818 Steps to reproduce 1.Login 2.Click menu 3.Click Death Certificate 4.Click on update status 5.Select Relationship to decedent