Docket Clerk: Forward Stipulated Decision (1.7)

[JessicaMarine]

As a Docket Clerk, in order to close a case, I want to review the Stipulated Decision.

Once the IRS Attorney submits the Stipulated Decision, it is received by a Docket Clerk. The Docket Clerk reviews the Stipulated Decision for obvious errors (checks to make sure the Stipulated Decision was submitted in the right case, signed by both sides, etc.). The Docket Clerk then forwards the Stipulated Decision to Senior Attorney for further action.

Pre-conditions:

• Work queue item has been created and has been assigned to specific docket clerk
• A Stipulated Decision is saved in the system.
• Docket Clerk is logged into the system.
• The Sr. Attorney that will receive the forward must already exist in the system

Acceptance Criteria:

• Docket clerk can see within the system that Stipulated Decision is ready to view. (Work queue - keep it simple until we have more user research for design)
• Docket clerk can view the Stipulated Decision.
• Docket clerk can forward the Stipulated Decision to a Sr. Attorney (or any other court user) for further action with a message to the Sr. Attorney
• Docket clerk gets success message that document was forwarded
• Sr. Attorney can see within the system (work queue) that Stipulated Decision is ready to view, along with the name of the person who sent it to them.
• Work queue item has been created and has been assigned to specific docket clerk (temporary by-pass; docket section will get added in future)

Notes

• Received date in work queue is the date the clerk receives the work item in their queue.
• Breadcrumb will mimic the back button.
  Notes from 12/20 design meeting:
• Blue bar indicates that box is scrollable
• Regarding the flow. Jessica felt Natalie's summary was spot on. It's closer to "B," the messaging board approach
• "Topic" - There isn't one. Threads don't have subject lines.
• User can only reply to the most recent message that's open
  *How do you know when a thread is complete? User clicks "complete"

Test Scenarios

• as a respondent, after I upload a stipulated decision to a case, a work item shall be made for the docketclerk user which is associated with that uploaded document, AND the work item shall appear on the docketclerks work queue
• as a docketclerk, I shall be able to click on the document that work item is associated with from my work queue and be redirected to the view document page
• as a docketclerk, on the view document page, I shall be able to see the latest message of the work item attached to the document.
• as a docketclerk, on the view documents page, I shall be able to forward a work item to another user (seniorattorney) and attach a new message to the work item, AND my work item should be removed from dockerclerk's work queue, AND the work item shall show up in the seniorattorney work queue

Tasks

• Design Docket Clerk Work Queue (Kristen/Sarah)
• Design Document Detail view (Kristen/Sarah)
• Design messaging/forwarding Work Queue-to-Work Queue (Kristen/Sarah)
• Create senior Attorney user (Kris)
• create docketclerk user (Kris)
• implement docketclerk work queue dashboard (same for sr attorney) (Kris)
• getWorkItem(s)/update sequence and action in cerebral (will)
• update work queue item sequence
• submit work queue item sequence
• test get all / get one / update work item sequences (Cody)
• move work queue sequence to dashboard sequence (Cody)
• add dynamic data to new dashboard work queues (Kris)
• getWorkItems GET PUT GET with id lambda (will - pr)
• getWorkItems interactor (returns workitems assigned to user either docketclerk or srattny) (will - pr)
• getWorkItems(userId) persistence method (Cody & Will)
• saveWorkItems in persistence method (Cody & Will)
• Design the Sr. Attorney dashboard/Work Queue (Kristen/Sarah)
• implement work item view (with forward button) (Eric)
• revisit tests for work item flow (confirm necessary tests) (Eric & Cody, UX Designers)

Definition of Done

• acceptance criteria have been met
• all code changes have been reviewed, approved, and merged and deployed to develop
• usability has been validated
• 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)
• 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]

@JessicaMarine @sadlerw @dubharmonic @uxforgood

Design for Docket Clerk work queue

• Docket Number
• Message column- display Document Title - as link. On click, links to Document Detail.
• Message text- will be blank for this story.
• Trial date - blank for this story
• Sent by - will show the party who uploaded the file - in this case Respondent
• Received - displays the date the work item entered the queue

[klohman]

@JessicaMarine @sadlerw @dubharmonic @uxforgood

Design for Senior Attorney Work Queue:

Same design as docket clerk queue.

Sent by= the user who sent / created the work item - in this case, the Docket Clerk (mockup includes a dummy name)

[klohman]

Document Detail page design

• When Docket Clerk clicks on the document title in their work queue, they are brought to this page.

The message in their work queue shows under Messages. When they click on Forward, the message card expands to show the 2 fields to send the message.

Send to - dropdown should contain all internal users.
On click of Forward, the Docket Clerk's work item is removed from their queue, and a new work item (message) is created in the Senior Attorney's work queue. Success message displays in document detail page with date and time sent. The new message will display with the option to "View History."

On click of View History, the message card expands to show the full message history.

On click of the Hide History- the previous messages would collapse.

@JessicaMarine @sadlerw @dubharmonic @uxforgood

[klohman]

@codyseibert @JessicaMarine

Updated design - removing the message history (until future story).