Court User: Creating a case on behalf of paper-filing petitioner

[mariahkannenberg]

As a Court User, in order to start a new case for a paper-filed Petition, I need the ability to create a new case in the System.

When a Petitioner submits a Petition in paper form, an internal Petitions Clerk must upload that Petition into the CMS. This includes entering all contact information and case metadata, as well as uploading any documents provided by the Petitioner. Once the internal Court User is done entering everything, the case should be treated just as if an external filer uploaded the Petition electronically.

Pre-Conditions

• Court User is logged into the System

Acceptance Criteria

• Court User must be able to indicate that they are starting a case for a Petitioner
• Court User must enter all contact information for Petitioner
• Court User must enter all case metadata for the Petitioner
• Court User must upload any required documents for the Petitioner
• Court User must be able to overwrite date that petition was received by Court for case creation/document upload
• System must store that this case was started as a paper petition (metadata stored for later reporting needs, but not displayed in UI)
• Court User must be able to confirm that a new case has been successfully started for a Petitioner
• When the case is created in the system issues the next sequential docket number
• When an internal user (Petitions Clerk or Docket Clerk) starts a new case from a paper petition, the new case is added to the user's work queue and to the user's section work queue as a work item. The work item should be assigned to the internal user who started it.
• The work item in the individual queue and section queue should contain the following message: "Petition filed by [Petitioner's name -- everything before the v. in the caption] is ready for review."

Notes

• Same interface as petitioner except doesn't need notifications and warnings

Research/Analysis Notes

Tasks

• [x] Design: Update petition's clerk dashboard
• [x] Design: Modify form design
• [x] Design: Update case info tab on case detail page
• [x] Code: Add "Create a Case" button to petition clerk dashboard/work queue (William #1219)
• [x] Code: Create "Create a Case" page for internal users (William #1236)
• [x] Code: Sequence and Tests for Petition from Paper (William #1232)
• [x] Code: Reduce validation requirements for a Petition Clerk on the Start a Case page (Kris & Eric #1221)
• [x] Code: Interactors, Lambda, Swagger (Eric #1231)
• [x] Code: Interactor tests (Cody)
• [x] Code: Update Petition QC Document Info tab for paper petitions (add Date Received, etc.) (Rachael #1228)
• [x] Code: Add ability for Docket Clerk to Start a Case in the same manner. (Rachael #1233)
• [x] Code: Interactor for Uploading files when submitting a Petition without Paper (Eric #1236)
• [x] Code: UI Integration
• [x] Code: make file selection icons consistent (Rachael)
• [x] Code: fix createdAt time
• [x] Code: take the user directly to document detail after case is created (William #1240)
• [x] Code: add isPaper and dateReceived to Case entity and store that info when case is created (Rachael, Cody #1243)
• [x] Code: add work item for user who created the case (Rachael, Cody)
• [x] Email of Internal User showing for Primary Contact on case detail page (Rachael)
• [x] Size of Caption Field changing in error state (Rachael)
• [x] Fee Payment Date Not Displaying when "Batched for IRS" (Rachael)
• [x] Notice /Case Type not showing in read-only view or case info tab (Rachael)

Definition of Done

Product Owner

• [ ] Acceptance criteria have been met

UX

• [x] Usability has been validated

Engineering

• [x] Field level and page level validation errors (front-end and server side) integrated and functioning
• [x] Run the browser stack scripts to verify that application is usable in Chrome, Firefox, Safari, Edge and Internet Explorer (external only)
• [x] No errors reported in manual a11y testing
• [x] All new functionality verified to work with keyboard and osx voiceover
• [x] Code refactored for clarity and to remove any known technical debt
• [x] README, other appropriate docs, and swagger/APIs fully updated - all code functions documented with jsdocs
• [x] UI should be touch optimized and responsive for external only(functions on supported mobile devices and optimized for screen sizes as required)
• [x] Library/module dependencies are up-to-date and are at the latest resolvable version
• [x] Code is deployed to DEV
• [x] Errors in sonarcloud are fixed (https://sonarcloud.io/organizations/flexion-github/projects)
• [x] Alerting and monitoring for new functionality in place and successfully exercised

[klohman]

@JessicaMarine Updated designs for internal case creation

Petition's clerk dashboard

• Add "Create a Case" button that takes user to the Create a Case form for internal Court users

Create a Case form

Internal Court users will see a form to upload documents to create a case.

Required Fields

• Date Received
• Case Caption
• Upload Petition

All other fields are optional.

Field-level validation for correct date inputs and not being in the future are for:

• Date Received

On click of Cancel button - discard all uploads and return user to their work queue.

On click of Create Case button:

• the new case is assigned the next sequential docket number
• the new case is added to the user's work queue and to the section work queue showing assigned to the user
• the new case is flagged as a paper petition (does not show in UI)
• the user is taken directly to the Document Detail page for the new petition

Document Detail Page

• caption displayed is the caption manually entered from previous page

Date Received

• Add Date Received field to the Case Info tab
• Date received field is only displayed for paper petitions
• Date received will be pre-populated with date entered in previous page but is editable
• Date must be in correct format and cannot be in the future

Ownership Disclosure Statement

For party type of Corporation, Partnership (Tax Matters Partner), Partnership (other than Tax Matters Partner), and Partnership (BBA Regime):

Display Ownership Disclosure Statement field

• if the ODS was uploaded on previous screen, display link (same functionality as on electronic petitions)
• If no ODS was uploaded, show "No file uploaded." message.

[klohman]

@rachaelparris

UX Review Notes

Email of Internal User showing for Primary Contact

• Email of the internal user who created the case is displaying under Primary Contact - for paper petitions, no email should display

Size of Caption Field changing in error state

(not related to this AC)

Fee Payment Date Not Displaying when "Batched for IRS"

• correct payment date displays in docket record

• no date is showing on Petition Document Detail page in read-only state

Notice /Case Type

• case type not showing on Document Detail when in read-only mode or on Case Info tab

[JessicaMarine]

PO review comments:

@uxforgood @klohman @sarahridgway

The flow is off. We need to "Start/Generate the case" only after ALL of the information is in. When a Petitions Clerk is changing the caption of case type on the QC screen, it should not auto-generate docket entries summarizing the changes. They are basically doing data entry at this point, and could need to correct it before the case data is corrected. This is different from when the Petitions Clerk is reviewing and correcting a case that has already been created electronically by a Petitioner.

[JessicaMarine]

I believe the idea is that if it came in today, it would display the time. But, after that day has passed, it would roll to the date of receipt.

From: mariahkannenberg [mailto:notifications@github.com] Sent: Friday, March 29, 2019 4:27 PM To: flexion/ef-cms ef-cms@noreply.github.com Cc: Marine, Jessica jfmarine@ustaxcourt.gov; Mention mention@noreply.github.com Subject: Re: [flexion/ef-cms] Court User: Creating a case on behalf of paper-filing petitioner (#311)

Petitions Clerk - Time showing up instead of date in inbox received field. Happening in section queue as well.

[image.png]https://camo.githubusercontent.com/5c641bccb91d5c9918fa65a89c0c0554704a0a0c/68747470733a2f2f696d616765732e7a656e68756275736572636f6e74656e742e636f6d2f3562633530316238363031363537313833313331636166332f32373063323762632d303232662d346165342d616165632d343064623832306537386233 [image.png]https://camo.githubusercontent.com/3ff02c3bca23163eb516ae5dd033714b98b05602/68747470733a2f2f696d616765732e7a656e68756275736572636f6e74656e742e636f6d2f3562633530316238363031363537313833313331636166332f64383363613663632d343335322d346632382d613830302d643137343839323632303233

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/flexion/ef-cms/issues/311#issuecomment-478138642, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Am-kqfYAXFPdTyTbcIpfTWcJig_rv-MLks5vbnb9gaJpZM4ZRfop.