Skip to content

Improve button text for import eligible registrant and Copy new beneficiaries from the program #640

@anthonymarkQA

Description

@anthonymarkQA

Describe the bug
As discused with BA, Import eligible registrant and copy beneficiaries from the program should be altered to import new eligible registrants and copy new beneficiaries from the program
This is to align what the buttons actually do.

As a user i will assume "import eligible registrant" means if a not eligible group is already in the program, then i edit that group to be qualified for the program, when i press it, it will also change the already imported group's status from not eligible to enrolled . because the group was eligible already.

therefore import new eligible registrants is a better fit since it tells the user, it can only add new groups/individuals in the program that qualify for the program.

The same problem with Copy beneficiaries from the program button. it can only copy new beneficiaries from the program.

To Reproduce

  1. Go to qa spmis and login as admin
  2. In registry, go to configuration and create a tag "tag a1"
  3. Assign this tag into two groups in registry
  4. Create a program that targets groups with "tag a1" and auto import and enroll.
  5. Inside your program, you should have 2 beneficiaries that have a status "enrolled"
  6. Go to registry and remove the tag a1 from one of the groups then save.
  7. Go back to program and click verify eligibility. This should change the unqualified group's state to not enrolled.
  8. Go back to registry and add "tag a1" back to the group then save
  9. Go back to program then click import eligible registrant. as user, you would mistakenly expected it will also change that group's status in the beneficiaries tab from 'not eligible' to 'enrolled' since you made the group able to qualify again.
    10

Expected behavior
Change button names to

  • Import New Eligible Registrants
  • Copy New Beneficiaries from Program

Screenshots
image
image

Additional context

🔔 Note: This ticket should address common considerations without including country-specific content. Please ensure all references are generic and applicable across various contexts.

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions