Petitioner: Upload IRS Notice (2.4)

[JessicaMarine]

As a Petitioner, in order for the Court to confirm it has jurisdiction, I need to upload my IRS Notice as part of my Petition package.

In addition to uploading a Petition form, Petitioner should be prompted to also upload their IRS notice(s) (if any) as part of the Petition package (only 1 upload function), so that when it is transmitted to the Court, the Petition and IRS notice should be part of the same PDF.

Pre-Conditions:

• Petitioner is logged into the System
• Petitioner has elected to “Start a New Case”

Acceptance Criteria:

• Petitioner is prompted to upload IRS notice as part of Petition.
• The Petition with IRS notice is viewable to internal users and both parties (Taxpayer and IRS) as one document on the docket record.

Notes

Tasks

• Redesign Start a case form to accommodate single petition file upload (Natalie, Kristen)
• remove irs notice from the view(s) (update ui to match design - remove progress indicators) (Kris)
• remove irs notice from entities and interactors and computeds etc.(both presenter and backend) (Eric)
• modify test scenarios to accommodate no irs notice (Eric)
• Make UI updates and changes to copy presentation (Eric & Natalie)

Business Test Cases

nothing new

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

[klohman]

revised Start a Case form