-
Notifications
You must be signed in to change notification settings - Fork 10
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
Practitioner: Generate Entry of Appearance Document for E-Filing #10054
Comments
Pre-refinement questions: |
Request access to case page
EA for Petitioner - Generate EA for Respondent - Generate EA for Respondent - Upload ”Review your filing”
Review - Practitioner Generated Review - Practitioner uploaded PDFS Petitioner estate Respondent
|
Test Cases1) Private Practitioner requests access to a case; Redaction text on the page is now displayed with a yellow background.
Expected Results:
*Repeat this test with an IRS Practitioner. 2) Private Practitioner selects all options besides Entry of Appearance from the document type dropdown; no option for Auto-generated document is available.
Expected Results:
*Repeat this test with an IRS Practitioner 3) Private Practitioner selects Entry of Appearance from the document type dropdown; New radio button option is available to Auto-Generate the Entry of Appearance PDF.
Expected Results:
*Repeat this test with an IRS Practitioner
4) Private Practitioner selects Auto-generate Entry of Appearance PDF, Clicks Review Filing.
Expected Results:
*Repeat this test with an IRS Practitioner
*Be sure to test this with a practitioner that has an international address to ensure that their address information appears on the Auto-Generated EA correctly 5) Private Practitioner submits the auto-generated EA document.
Expected Results:
*Repeat this test with an IRS Practitioner
6) Docket Clerk QC's the auto-generated EA document.Part 1
Expected Results
Part 2
Expected Results:
*Repeat this test by also clicking complete and send message 7) Private Practitioner uploads and then submits the uploaded EA documentPart 1
Expected Results:
Part 2
Expected Results:
*Repeat this test as an IRS Practitioner. 8) Docket Clerk QC's the uploaded EA document
Expected Results:
*Be sure that you can QC an uploaded EA from both a Private Practitioner AND an IRS practitioner 9) IRS Respondent submits an uploaded EA document and files it across the group of consolidated cases; document is filed in each case appropriately
Expected Results:
Part 2
Expected Results:
10) Docket Clerk QC's the Uploaded EA document that was filed across the group
Expected Results:
11) Complete the Practitioner tests above on a mobile device
|
Some testing feedback: If the user takes more than 2 minutes (I think) on the Review your Filing page to click on the Document preview link: They will get this error message: And then when they attempt to submit the EA to the Court, they will get the Uh-oh error message with this error: |
@TomElliottFlexion @zRogersFlexion @codyseibert Some more testing feedback:
|
As a practitioner, so that I can easily file entries of appearance, I need a workflow that assembles and files an entry of appearance form for me.
The form for an Entry of Appearance (EA) form largely contains information already known by DAWSON; in order to make filing these as easy as possible, we would like to give practitioners an option to simply indicate the party(s) on whose behalf they are making an appearance, then have DAWSON assemble the completed form for approval and filing. This only applies to EA documents; Limited Entry of Appearance and any other documents that appear as selections in the Request Access to This Case workflow are not in scope.
To begin, we will implement this without the ability to multidocket these forms across a consolidated group.
Pre-Conditions
Acceptance Criteria
Notes
https://app.zenhub.com/files/152320868/a8581d06-4690-4db4-ae57-c4dd9c852444/download
https://app.zenhub.com/files/152320868/97354ce2-82d1-4fc4-911a-693e5b15872f/download
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
test
environment if prod-like data is required. Otherwise deployed to anyexperimental
environment.staging
environment.The text was updated successfully, but these errors were encountered: