Skip to content
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

Court: Suffix on Docket Number (2.6) #404

Closed
22 tasks done
JessicaMarine opened this issue Dec 18, 2018 · 0 comments
Closed
22 tasks done

Court: Suffix on Docket Number (2.6) #404

JessicaMarine opened this issue Dec 18, 2018 · 0 comments
Labels
Milestone

Comments

@JessicaMarine
Copy link

JessicaMarine commented Dec 18, 2018

As the Court, in order for the Docket Number to be accurately identify the case, I need a suffix added to the end of a docket number where appropriate.

If a Petitioner elects to have their case conducted as a “small” case, or selects certain types of cases (i.e., CDP, Whistleblower), a suffix needs to be added to the end of the docket number. See Notes for specific rules.

Pre-Conditions:

  • Petitioner has selected the type of Case (Deficiency, Collection Due Process, Innocent Spouse, Whistleblower, etc.)
  • Petitioner has selected whether they want case conducted as Small v. Regular
  • Petitioner has submitted case to Court

Acceptance Criteria:

  • The auto-generated docket number has a suffix if certain conditions are met [see Notes for rules]

Tasks:

  • 1. Implement the docket number logic into the docket number creation function (will/cody pr)
  • 2. Modify search to remove the suffix when a user searches a docket number (will/cody pr)
  • 3. Create cerebral computed for display of docket number with the suffix (cody pr)

Business Tests

  • when a case is created the docket number suffix is created according to the rules
  • when any user views a docket number anywhere in the system the suffix displays with the docket number

Notes:

  • If Petitioner elects “small” tax case procedures, a “S” is added to the end of the Docket Number
  • If Petitioner elects “Lien/Levy” as case type, a “L” is added to the end of the Docket Number
  • If Petitioner elects “Whistleblower” as case type, a “W” is added to the end of the Docket Number
  • If Petitioner elects “Passport” as case type, a “P” is added to the end of the Docket Number
  • If Petitioner elects “Declaratory judgments for Exempt Orgs” as case type, a “X” is added to the end of the Docket Number
  • If Petitioner elects “Declaratory Judgment for retirement plan revocation” as case type, a “R” is added to the end of the Docket Number
  • Special Case: If a Petitioner elects “small” tax case, as well as “lien/levy” as case type, the “S” for small tax case should proceed the “L” for the case type. For example, a docket number would be 12345-18SL. (The “SL” suffix is unique; the “S” is not combined with any other suffix. In any other case, if “S” and another suffix are both relevant, only the other suffix displays.)
  • Suffix is always uppercase

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants