IRS Attorney: Submit Stipulated Decision (1.6)

[JessicaMarine]

As an IRS Attorney, in order to settle a case, I want to submit a Stipulated Decision.

After the Answer is filed and the case is “at issue”, the IRS Attorney and Petitioner have settlement discussions without the Court’s involvement. Before Petitioner’s trial is scheduled, Petitioner convinces the IRS that the deductions she claimed are correct. Petitioner and the IRS Attorney agree to a written settlement (Stipulated Decision) and both sign it. The IRS Attorney then submits a PDF of the Stipulated Decision to the Court capturing the relevant details of the settlement.

Pre-conditions:

• IRS Attorney is logged into the system.
• Stipulated Decision signed by both parties is saved as PDF.
• IRS Attorney knows the docket # of the case.
• IRS Attorney has filed an Answer (not always required).
• IRS Attorney can search for the case by docket # (or is on attorney’s case list).

Acceptance Criteria (Post-conditions):

• The system knows that the user is an IRS Attorney.
• Stipulated Decision is saved in the system.
• Stipulated Decision is associated with the correct case (Docket #).
• IRS Attorney and Petitioner can view a record of the filing (PDF) in the system in the correct case.

Tasks

• Create Upload view(Same as IRS Attorney: File Answer (1.5) #111 ) (cody)
• create a work queue record after submit (cody)
• discuss current code with team and try to "clean" up if possible (cody / will)
• fix filedBy to show Respondent for irs and Petitioner for petitioner (will)

Definition of Done

• acceptance criteria have been met
• all code changes have been reviewed, approved, and merged and deployed to develop
• all automated unit tests are passing on all supported browsers with coverage > 90%
• run the browser stack scripts to verify that application is usable in Chrome, Firefox, Safari, Edge and Internet Explorer
• all automated a11y checks are passing - no new WCAG2.1 or AA contrast issues present
• 0 errors reported in manual a11y testing
• all new functionality verified to work with keyboard and osx voiceover
• all code quality checks are passing - sonar, eslint, html validation, etc.
• code refactored for clarity and to remove any known technical debt
• application can be deployed to multiple regions
• README, other appropriate docs, and swagger/APIs fully updated - all code functions documented with jsdocs
• performance tests successfully completed and no new significant performance issues found
• alerting and monitoring for new functionality in place and successfully exercised
• ui should be touch optimized and responsive (functions on supported mobile devices and optimized for screen sizes as required)
• usability has been validated
• npm audit for CVE’s in production library/module dependencies identified and resolved
• library/module dependencies are up-to-date and are at the latest resolvable version