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

As a Cif User, I want the list of contacts in the project-contacts dropdown to be disambiguated, so that I can see the difference between contacts with the same name #1863

Open
17 tasks
dleard opened this issue Sep 6, 2023 · 0 comments
Labels
Backlog Refinement Tickets that require further refinement User Story A User Story issue type

Comments

@dleard
Copy link
Contributor

dleard commented Sep 6, 2023

Description:

Our dropdown currently only shows first_name - last_name in the options. This can be confusing if there end up being contacts with the same name, but are in fact different. If we show the email address along with the name, then we will be able to disambiguate contacts with the same name

Acceptance Criteria:

Given I am on the project-contacts tab of a project
When I use the project-contacts selection dropdown
Then I can see the email address as well as the names of the contacts in the dropdown options

Development Checklist:

  • update the displayed options in the project-contacts dropdown to show the email address of the contact

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

  • User story is included
  • User role and type are identified
  • Acceptance criteria are included
  • Wireframes are included (if required)
  • Design / Solution is accepted by Product Owner
  • Dependencies are identified (technical, business, regulatory/policy)
  • Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

  • Acceptance criteria are tested by the CI pipeline
  • UI meets accessibility requirements
  • Configuration changes are documented, documentation and designs are updated
  • Passes code peer-review
  • Passes QA of Acceptance Criteria with verification in Dev and Test
  • Ticket is ready to be merged to main branch
  • Can be demoed in Sprint Review
  • Bugs or future work cards are identified and created
  • Reviewed and approved by Product Owner

Notes:

@dleard dleard added Backlog Refinement Tickets that require further refinement User Story A User Story issue type labels Sep 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog Refinement Tickets that require further refinement User Story A User Story issue type
Projects
None yet
Development

No branches or pull requests

2 participants