IRS Practitioner changes their Email to non-IRS/DOJ

[mmarcotte]

As an IRS Practitioner who is leaving the IRS or Department of Justice, so that I can ensure a smooth transition and avoid conflicts of interest, I need to remove myself from all of the cases I am currently the respondent before proceeding.

Pre-Conditions

Acceptance Criteria

• If an IRS Practitioner changes their Email address from @*.irs.gov, @*.doj.gov, @*.treas.gov to a non-IRS/DOJ Email Address and they are associated with cases, DAWSON needs to inform them they need to withdraw from cases in order to complete the operation.

Maybe this manual process can be automated (see comment below)?

• If an IRS Practitioner changes their Email address from @*.irs.gov, @*.doj.gov, @*.treas.gov to a non-IRS/DOJ Email Address and they are NOT associated with cases, DAWSON should complete the operation, but then prevent them from filing documents UNTIL Admissions Clerks change their Employer. The user should be notified as such.
• Admissions Clerk should get a [Work Item? Message?] notifying them of the IRS Practitioner changing their Employer to Private to complete the operation
• Once the operation is complete, the user should be notified by Email that they can no longer file on behalf of the IRS and are now a Private Practitioner

Pre-Conditions

Acceptance Criteria

Mobile Design/Considerations

IRS API Considerations

Do these changes impact the IRS API?

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

Definition of Done (Updated 4-14-21)

Product Owner

• [ ] Acceptance criteria have been met and validated on the Court's migration environment
• [ ] Add scenario to testing document, if applicable (https://docs.google.com/spreadsheets/d/1FUHKC_YrT-PosaWD5gRVmsDzI1HS_U-8CyMIb-qX9EA/edit?usp=sharing)

UX

• [ ] Business test scenarios to meet all acceptance criteria have been written
• [ ] Usability has been validated
• [ ] Wiki has been updated (if applicable)
• [ ] Story has been tested on a mobile device (for external users only)

Engineering

• [ ] Automated test scripts have been written
• [ ] Field level and page level validation errors (front-end and server-side) integrated and functioning
• [ ] Verify that language for docket record for internal users and external users is identical
• [ ] New screens have been added to pa11y scripts
• [ ] All new functionality verified to work with keyboard and macOS voiceover https://www.apple.com/voiceover/info/guide/_1124.html
• [ ] READMEs, other appropriate docs, JSDocs and swagger/APIs fully updated
• [ ] UI should be touch optimized and responsive for external only (functions on supported mobile devices and optimized for screen sizes as required)
• [ ] Interactors should validate entities before calling persistence methods
• [ ] Code refactored for clarity and to remove any known technical debt
• [ ] Acceptance criteria for the story has been met
• [ ] Deployed to any Flexion environment for UX Review
• [ ] Deployed to the Court's migration environment

[mmarcotte]

Does it have to be a manual process? Can (and should) the system be smart enough to just change their employer if they're not associated with any open cases?

Would be helpful to add extra confirmation when performing this operation.