As a DOJ employee, so that I do not enter appearances in cases that I shouldn't have access to, I need to only be able to represent parties in cases that are in the status On Appeal.
Recently, the Court has seen DOJ attorneys requesting access to cases where the lawyer is not representing a party on appeal. This is prohibited by Court policy, so we want to restrict this via code to prevent this from occurring again.
Pre-Conditions
Acceptance Criteria
IRS practitioner users with an Employer value of "DOJ" do not see the "Represent a Party" button when viewing a case unless the Status of the case is "On Appeal".
Notes
Tasks
Test Cases
Story Definition of Ready (updated on 12/23/22)
The following criteria must be met in order for the user story to be picked up by the Flexion development team.
The user story must:
[ ] Is framed in business/user need, the value has been addressed.
[ ] Includes acceptance criteria
[ ] Has been refined
[ ] Pre conditions have been satisfied.
Process:
Flexion developers and designers will test if the story meets acceptance criteria and test cases in Flexion dev and staging environments (“standard testing”). If additional acceptance criteria or testing scenarios are discovered while the story is in progress, a new story should be created, added to the backlog and prioritized by the product owner.
Definition of Done (Updated 5-19-22)
Product Owner
[ ] Acceptance criteria have been met and validated on the Court's migration environment
[ ] READMEs, other appropriate docs, 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.
[ ] If new docket entries have been added as seed data to efcms-local.json, 3 local s3 files corresponding to that docketEntryId have been added to web-api/storage/fixtures/s3/noop-documents-local-us-east-1
[ ] Acceptance criteria for the story has been met.
[ ] If there are special instructions in order to deploy into the next environment, add them as a comment in the story.
[ ] If the work completed for the story requires a reindex without a migration, or any other special deploy steps, apply these changes to the following flexion branches:
[ ] experimental1
[ ] experimental2
[ ] experimental3
[ ] experimental4
[ ] experimental5
[ ] experimental6
[ ] develop
[ ] Reviewed by UX on a deployed environment.
[ ] Reviewed by PO on a deployed environment. Can be deployed to the Court's test environment if prod-like data is required. Otherwise deployed to any experimental environment.
1) DOJ Attorney enters an appearance on a case where the case status is "On Appeal", Attorney is added to the case as per normal.
Preconditions: Be sure that you have a log in for a DOJ attorney
Log in as the DOJ attorney
Navigate to a case whose status is "On Appeal"
Expected Results:
[ ] The Represent a party button is displayed at the top right of the screen as per normal
[ ] After clicking on the Represent a Party button, the DOJ practitioner is able to enter an appearance as per normal
[ ] Attorney can generate the EA if all parties receive electronic service
[ ] Attorney can upload the EA
[ ] Docket record reflects the EA document as per normal, service is sent as per normal.
2) DOJ Attorney navigates to a case that is not on Appeal; The Represent a Party button is not available and is not displayed.
Preconditions: Be sure that you have a log in for a DOJ attorney
Log in as the DOJ attorney
Navigate to a case whose status is anything but "On Appeal"
Expected Results:
[ ] NEW FUNCTIONALITY - The Represent a party button is NOT displayed at the top right of the screen.
[ ] NEW FUNCTIONALITY - DOJ Attorney is not able to file any type of document on the case.
*Be sure that you test with Every Case Status.
[ ] New
[ ] General Docket - Not at Issue
[ ] General Docket - At Issue - Ready for Trial
[ ] Calendared
[ ] Submitted
[ ] Submitted - Rule 155
[ ] Jurisdiction Retained
[ ] Closed
[ ] Closed - Dismissed
[ ] Assigned - Case
[ ] Assigned - Motion
[ ] CAV
3) DOJ Attorney navigates to a case that was once On Appeal, but is no longer on Appeal (closed); DOJ attorney no longer sees the "Represent a Party button)
Preconditions: Be sure that you have a log in for a DOJ attorney
Log in as the DOJ attorney
Navigate to a case whose status is "On Appeal"
You will see the Represent a Party button
Next, log out and back in as a docket clerk
Change the case status to anything other than On Appeal
Log back in as the DOJ Attorney
Navigate to the case from above that was previously on appeal
Expected Results:
[ ] NEW FUNCTIONALITY - The Represent a party button is NOT displayed at the top right of the screen.
[ ] NEW FUNCTIONALITY - DOJ Attorney is not able to file any type of document on the case.
4) Regression test to ensure the following:
[ ] IRS attorney's can still enter an appearance on cases that are in any case status
[ ] Private Practitioners can still enter an appearance on cases that are in any case status
[ ] Private, IRS, and Petitioners, Intervenors, Participants can still file documents on any case, regardless of case status
[ ] Sealed cases remain sealed, and if the user is not already a party, they cannot see the docket record or file documents.
As a DOJ employee, so that I do not enter appearances in cases that I shouldn't have access to, I need to only be able to represent parties in cases that are in the status On Appeal.
Recently, the Court has seen DOJ attorneys requesting access to cases where the lawyer is not representing a party on appeal. This is prohibited by Court policy, so we want to restrict this via code to prevent this from occurring again.
Pre-Conditions
Acceptance Criteria
Notes
Tasks
Test Cases
Story Definition of Ready (updated on 12/23/22)
The following criteria must be met in order for the user story to be picked up by the Flexion development team. The user story must:
Process: Flexion developers and designers will test if the story meets acceptance criteria and test cases in Flexion dev and staging environments (“standard testing”). If additional acceptance criteria or testing scenarios are discovered while the story is in progress, a new story should be created, added to the backlog and prioritized by the product owner.
Definition of Done (Updated 5-19-22)
Product Owner
UX
Engineering
efcms-local.json
, 3 local s3 files corresponding to that docketEntryId have been added toweb-api/storage/fixtures/s3/noop-documents-local-us-east-1
test
environment if prod-like data is required. Otherwise deployed to anyexperimental
environment.staging
environment.