search

bcgov / foi-flow

Freedom of Information modernization
Apache License 2.0
5 stars 3 forks source link

View and Select existing Applicant Profile #4761

Open lmullane opened 10 months ago

lmullane commented 10 months ago

Assumptions & Scope What are the assumptions for this story?

This story is only for the selection of an applicant profile when the applicant only has one profile (e.g. category) associated with the name of the individual.

View and selection will be a continuation of the search in story for applicant profiles in #4758

If an applicant has a new entered new contact information when making the new FOI request (e.g. a new email) and the analyst matches the applicant to an existing Applicant Profile that has different contact information (e.g. an old email), when the analysts Selects the existing Applicant Profile, then the Applicant Profile will be updated with the new contact information (e.g. email).

A request cannot be put in the 'Open' state until an applicant profile is matched to the request.

To edit Address and Contact Information for a request, the analyst must edit the Applicant Profile. This will ensure that the Applicant Profile (primary) is not out of sync with the request address and contact info (secondary).

What is IN scope? Navigate to applicant profiles from search results View the applicant profiles Select an existing applicant profile (when there is only one category for the applicant) Multiple applicant category profiles #4763

What is NOT in scope? Search Applicant Profile #4758 Multiple and new applicant category profiles #4763 Creating a new applicant profile Updating an existing applicant profile Request History for an applicant Applicant Contact History

Acceptance Criteria

Scenario 1: Click search result in Search Applicants profile

Scenario 2: Back to Search from Applicant Profile

Scenario 3: All information does not match

Scenario 4: All information does match

Scenario 5: Click Select Profile button

Scenario 6: Click 'X' on the' Add Applicant Profile to Request' modal will open

Scenario 7: Click 'Save Changes for All Open Requests' and all the information matches

Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)

Validation Rules? (If yes, list here)

Design @xxx - please link the Design here

Definition of Ready

  1. [ ] Is there a well articulated User Story?
  2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
  3. [ ] If there is a user interface, is there a design?
  4. [ ] Does the user story need user research/validation?
  5. [ ] Does this User Story needs stakeholder approval?
  6. [ ] Design / Solution accepted by Product Owner
  7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
  8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
  9. [ ] Has the story been estimated?

Definition of Done

  1. [ ] Passes developer unit tests
  2. [ ] Passes peer code review
  3. [ ] If there's a user interface, passes UX assurance
  4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
  5. [ ] Confirm Test cases built and succeeding
  6. [ ] No regression test failures
  7. [ ] Test coverage acceptable by Product Owner
  8. [ ] Ticket ready to be merged to master or story branch
  9. [ ] Developer to list Config changes/ Update documents and designs
  10. [ ] Can be demoed in Sprint Review
  11. [ ] Tagged as part of a Release
  12. [ ] Feature flagged if required
  13. [ ] Change Management activities done?
lmullane commented 10 months ago

Scenarios 3 and 4 were in the designs but are they necessary?

lmullane commented 10 months ago

@JHarrietha-AOT, please review.

Question for you - if an applicant submits a request and they have new contact information (e.g. a new phone number). When the IAO analyst finds and the selects an existing Applicant Profile and saves that profile to the request, then which contact information would be used? Would the new phone number be added to the existing Applicant Profile, or would the existing phone number overwrite the new number provided by the applicant with their FOI request?

cc @arielleandrews @m-prodan

Answer to the above was that the new information provided in the new FOI request will supercede the information on the existing Applicant Profile. See AC in comment below.

lmullane commented 10 months ago

As discussed will remove scenarios for updating applicant profile when the information on the original request does not match the information on the Applicant Profile (e.g. email).

The AC below are included in an Edit and Save Applicant Profile story (#4769):

Scenario 8: Click 'Save Change for Current Request' when all information DOES NOT match

Scenario 10: Click 'Save Changes for All Open Requests' and all the information DOES NOT match

abin-aot commented 10 months ago

View and Select existing Applicant Profile#4761 - 8/13 ##################################################

front end - 3

Switch over of views from "Search Applicants" to "Applicant Profile" develop react components for "Applicant Profile" - Viewonly

back end

API to fetch the Applicant details as per selection on the list - 5

JHarrietha-AOT commented 9 months ago

@lmullane Story needs to be updated with the new module we discussed at Stand-Up yesterday. It is the module that will show up if the Analyst Clicks to Create New Profile. I added it in the flow here (under sprint 66: https://miro.com/app/board/uXjVMtjQyiU=/?share_link_id=207208780832). Let me know if you have any questions