Petitioner without Existing Account: Verifies Email and Gains Electronic Access to Case

[mariahkannenberg]

As a petitioner, so that I may gain access to the DAWSON system, I need the ability to verify my account.

Pre-Conditions

7806

Acceptance Criteria

• Single petitioner is able to verify their Cognito account and gain access to the system
• When a user is linked to a case (either through the new Cognito account or linkage to existing one), they have access to the case:
  • It shows on their dashboard
  • They have the associated view
  • They can e-file documents
  • Once the petitioner has verified their email, service information is updated to "electronic"
    • Once the petitioner has verified their email, they begin receiving electronic service at the email that was added

Mobile Design/Considerations

Security Considerations

• [ ] Does this work make you nervous about privacy or security?
• [ ] Does this work make major changes to the system?
• [ ] Does this work implement new authentication or security controls?
• [ ] Does this work create new methods of authentication, modify existing security controls, or explicitly implement any security or privacy features?

Notes

Tasks

• [x] Check for PostAuthentication_Authentication trigger - Mrachael #7882
  • [x] check user by Id from persistence for pending email. If pending email matches login email- #7882
  • [x] update user.email to be value of pending email #7882
  • [x] update case.contactPrimary.email #7882
  • [x] change service preference of contact primary to electronic #7882
  • [x] verify electronic service emails for that email #7882
  • [x] All associated cases show up on petitioner dashboard #7882
  • [x] Petitioner can e-file documents on the case #7882
  • [x] Petitioner can view the case #7882
• [x] On email verification, party view of case information tab - Mrachael #7885
  • [x] Hide pending email view
  • [x] Remove party type view
  • [x] Hide current email field #7885
• [x] On email verification, internal view of case information tab #7885
  • [x] Hide pending email view #7885
  • [x] Display Current email field #7885

Definition of Done (Updated 2-23-21)

Product Owner

• [x] Acceptance criteria have been met and validated on the Flexion Prod env

UX

• [x] Business test scenarios to meet all acceptance criteria have been written
• [x] Usability has been validated
• [x] Wiki has been updated (if applicable)
• [ ] Story has been tested on a mobile device (for external users only)
• [x] Add scenario to testing document, if applicable (https://docs.google.com/spreadsheets/d/1FUHKC_YrT-PosaWD5gRVmsDzI1HS_U-8CyMIb-qX9EA/edit?usp=sharing)

Engineering

• [x] Automated test scripts have been written
• [x] Field level and page level validation errors (front-end and server-side) integrated and functioning
• [x] Verify that language for docket record for internal users and external users is identical
• [x] New screens have been added to pa11y scripts
• [x] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
• [x] READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated
• [x] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
• [x] Module dependencies are up-to-date and are at the latest resolvable version (npm update)
• [x] Errors in Sonarcloud are fixed https://sonarcloud.io/organizations/flexion-github/projects
• [x] Lambdas include CloudWatch logging of users, inputs and outputs
• [x] Interactors should validate entities before calling persistence methods
• [x] Code refactored for clarity and to remove any known technical debt
• [x] Rebuild entity documentation
• [x] Acceptance criteria for the story has been met
• [x] Deployed to the dev environment

• [x] Deployed to the Court's migration environment

  Review Steps

  1. Finish all other DOD
  2. Deploy to the dev environment
  3. Engineers add Needs UX Review label
  4. UX Review on dev environment (if feedback, implement and go back to step 2)
  5. UX add Needs Migration Deploy label
  6. Deploy to the Court's migration environment
  7. Engineers go through test scenarios on Court's migration environment
  8. Engineers add Needs PO Review label and move to Review/QA column
  9. PO review (if feedback, implement and go back to step 2)

[klohman]

Petitioner receives new account email and verifies (aka, logs into system for first time) email

External Party View: Case Detail > Petitioner

Once email is verified

• Remove party type
• Update field locations based on design
• Hide current email field for party view

Internal User View - Case Detail > Petitioner

Once email is verified

• Display current email address Note: Seal address button should only display for docket clerks (this is current functionality)

Edit Petitioner Info - with email

Service preference options include:

• Electronic (if email is saved and verified)

• Paper

• None

• Display Current email address

[klohman]

7807 Test Scenarios

1) Petitioner (primary contact) without existing account is added to case and verifies email

• Login as admissions clerk
• Go to case xx3-20
  • Case has party type = Petitioner & Spouse
  • Petitioner & Spouse have no email and paper service
• Click Case Information > Petitioner
• Click edit link for primary contact
• Enter and re-enter new email = [new email]
  • Dev - flexionustc+newemail@gmail.com
• Click Save
• Click Yes, Continue
• Go to petitioner email account
  • Dev = flexionustc+newemail@gmail.com
• Click the login link
• Update password and login
• Click Docket number for case xx3-20 Expected results
• [x] case xx3-20 displays in My Cases on dashboard
• [x] petitioner service indicator displays as Electronic for case xx3-20
• [x] email displays under My Account> Login & Service email

2) Admissions clerk adds email to case and petitioner (primary contact) receives electronic service for party-filed document after the email is verified

• Scenario 1
• Login as irs practitioner
• Search for case xx3-20
• File Answer Expected results
• [x] Petitioner primary contact service preference displays as Electronic
• [x] Petitioner primary contact receives service email at new email account

3) Admissions clerk adds email to case and petitioner (primary contact) receives electronic service for court-issued document after email is verified

• Scenario 1
• Login as docket clerk
• Create, sign, and save Order
• Add Docket entry for Order
• Save and Serve Expected results
• [x] Petitioner primary contact receives service email at new email account

4) Petitioner (primary contact) without existing account is added to case, verifies email, and internal users see current email

• Scenario 1
• Login as internal user
• Go to case xx3-20
• View Case Info> Petitioner
• Login as docket clerk / admissions clerk
• Go to case xx3-20
• View Case Info> Petitioner
• Click Edit link on Petitioner card Expected results On Petitioner card:
• [x] Petitioner current email displays as flexionustc+newemail@gmail.com
• [x] petitioner service preference displays as Electronic On edit Petitioner form
• [x] Petitioner current email displays as flexionustc+newemail@gmail.com
• [x] petitioner service preference displays as Electronic

[JessicaMarine]

@rachaelparris and team PO Review 3/1/2021:

1. There is duplicate docket entry language showing up on the P's and IRS' view of the docket record once a petitioner sets up his/her account following the full flow:

Before adding email on P:

After adding email on P:

Duplicate docket entry language displays on P’s and R’s view of the case. It does not display like this for internal users or public (see also 14000-20 on mig):

2. Petitioner's email address is not displaying on P's or IRS' view of the case:

It does show up for internal users:

[mrinsin]

@JessicaMarine regarding the second feedback point -I believe the AC says that external parties don't see the updated current email

[klohman]

@Mrinalini Sinha msinha@flexion.us @Marine, Jessica jfmarine@ustaxcourt.gov I had removed the email from the external view (because they would edit it from their My Account screen) but that won't work for the other parties on the case. Do we just want to show external users the same view as internal?

On Mon, Mar 1, 2021, 2:59 PM Mrinalini Sinha notifications@github.com wrote:

@JessicaMarine https://github.com/JessicaMarine regarding the second feedback point -I believe the AC says that external parties don't see the updated current email

[image: image] https://user-images.githubusercontent.com/20514925/109551438-cb04d100-7a8d-11eb-9705-1d8777893046.png

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/flexion/ef-cms/issues/7807#issuecomment-788229165, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEMD54E4EV2VZOLORAMP2UTTBPWYNANCNFSM4XY2J5JQ .

--

Notice: The information contained in this message or any attached document is confidential and intended only for individuals to whom it is addressed. If you got this message in error, please inform me immediately using one of the methods above. In some cases, I may ask you to return the documents at my expense. In general, please simply destroy the information at once. Any unauthorized use, distribution, or copying of this information is prohibited.

[JessicaMarine]

@klohman @mrinsin yes ^^^ ok to show external users the same view of this card as internal

[klohman]

UX review of PO feedback - Ready for PO re-review

• Duplicate language on docket record no long displays for IRS attorney or Petitioner view

• Petitioner email now displays for parties

[JessicaMarine]

PO Review:

• I went through the whole flow of 7806 and 7807 and everything worked great. I wanted to test how things looked on the printable docket records if P's address was sealed, so I went back into the case where P was now getting electronic service and sealed the address. It still showed as electronic service for internal users, but when I logged in as P (and the IRS attorney associated with the case), the service preference had changed to paper.
• Going to log as separate bug