Petitioner: Evidence warning

[JessicaMarine]

As the Clerk of the Court, in order to prevent Petitioners from filing evidence prematurely, I need the system to inform petitioners when they are uploading documents that evidence is not accepted until the time of trial.

Parties, especially unrepresented taxpayers, often try to send evidence in support of their case to the Court. Evidence is generally NOT accepted by the Court until the time of trial. In order to remind Petitioners that evidence should be submitted during their trial and that any evidence submitted before then will be disregarded, the filer should be reminded of this each time they try to file a new document. [Note: The Court currently issues a notice to a party AFTER they improperly submit evidence. I've included the language of that notice in a comment below. This language may be helpful in drafting the language for this warning.]

Pre-Conditions

• Petitioner is trying to upload/file a new document with the Court

Acceptance Criteria (Post-Conditions)

• Petitioner is informed that they should not submit any evidence to the Court until their trial every time they upload a document to the system.

Notes

Tasks

• Design of the premature evidence messaging and warning
• Develop business use test cases
• Implement view changes

Definition of Done

• acceptance criteria have been met
• Field level and page level validation errors (front-end and server side) integrated and functioning
• 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

[JessicaMarine]

This is the language that the Court currently uses to notify parties that they have submitted evidence prematurely. Perhaps it could be helpful is designing this warning language:

[tjcurington]

This story is completed with issue #644