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

Petitions Clerk: Review Party Type, Contact Information, and other Metadata #699

Closed
33 of 34 tasks
JessicaMarine opened this issue Jan 24, 2019 · 1 comment
Closed
33 of 34 tasks

Comments

@JessicaMarine
Copy link

JessicaMarine commented Jan 24, 2019

As a Petitions Clerk, in order to ensure that case metadata is accurate, I need the ability to review, edit and save Party Type and Contact Info.

As part of the QC process, a Petitions Clerk needs to be able to review, edit, and save the party type and contact information entered by Petitioner.


Pre-Conditions

Acceptance Criteria

  • Petitions Clerk can view all of the data that a petitioner has entered when starting a new case
  • Petitions Clerk can edit and save all fields (except for email address)
  • If Petitions Clerk makes a change that affects the docket number (i.e., case type or small/regular), that change is captured on the docket record as an entry that reads: "Docket Number is amended from [old docket number] to [new docket number]"
  • When the court changes the data originally entered by the petitioner, internal Court users can see the updated information on the Case Information tab.

Research/Analysis Notes

Tasks

  • 1. Redesign the QC page to accommodate the metadata (Kristen)
  • 2. Create new tabs (william)
  • 3. Party View (rachael, kris)
  • 4. Case Info View (cody)
  • 5. IRS Notice View (cody)
  • 6. Validation on entities and use case (no required fields) (kris)
  • 7. Create the entry into the docket record (William, Cody)
  • 8. Party View tab scrollable (Rachael)
  • 9. ODS link (Rachael)
  • 10. update docket number suffix on the case and work items (Cody)
  • 11. add autosave to all fields (Rachael)
  • 12. revisit autosave on caseProcedure and hasNotice after validation is removed (Rachael, Kris) - PR ready
  • 13. update the docketNumber in the page title after a suffix is updated (basically just set the caseDetail to match the case returned after an autosave update)
  • 14. Update docket record view to display updated docket record (William)
  • 15. Save when sending to IRS (Eric)
  • 16. Fix bug in which case caption is updated upon petitions clerk updating party type (kris)

Definition of Done

  • Jessica
    • acceptance criteria have been met
  • UX
    • usability has been validated
  • Engineering
    • Field level and page level validation errors (front-end and server side) integrated and functioning
    • run the browser stack scripts to verify that application is usable in Chrome, Firefox, Safari, Edge and Internet Explorer
    • 0 errors reported in manual a11y testing
    • all new functionality verified to work with keyboard and osx voiceover
    • code refactored for clarity and to remove any known technical debt
    • README, other appropriate docs, and swagger/APIs fully updated - all code functions documented with jsdocs
    • ui should be touch optimized and responsive (functions on supported mobile devices and optimized for screen sizes as required)
    • library/module dependencies are up-to-date and are at the latest resolvable version
  • CI/CD
    • npm audit for CVE’s in production library/module dependencies identified and resolved
    • application can be deployed to multiple regions
    • all automated a11y checks are passing - no new WCAG2.1 or AA contrast issues present
    • all automated unit tests are passing on all supported browsers with coverage > 90%
    • all code changes have been reviewed, approved, and merged and deployed to develop
    • all code quality checks are passing - sonar, eslint, html validation, etc.
  • Other
    • alerting and monitoring for new functionality in place and successfully exercised
    • performance tests successfully completed and no new significant performance issues found
@JessicaMarine JessicaMarine added the (2) DD Workflow - Petition Epic 2: Document Driven Workflow (Petition) label Jan 24, 2019
@tjcurington tjcurington added this to the Sprint #9 milestone Feb 20, 2019
@uxforgood uxforgood added the Design Needed Design work will be needed and development work should not start yet label Feb 20, 2019
@klohman
Copy link

klohman commented Feb 22, 2019

Updated Petition Document Detail Page

Document Info Tabs

  • Updated design of Document Info tab to include three sub-tabs (use secondary level tabs from style guide)
  • Tab order - Parties, Case Info, IRS Notice
  • the QC panel will be a fixed height to align with the PDF iframe, with vertical scrolling within the panel

Parties Tab

image.png

  • Includes all of the Party Contact Information - as built out in 307
  • Party Type field is editable and includes all party types
  • the contact fields displayed are dependent on the party type selected (see Figma file for mockups for each party type- the fields should map directly to what the user selects in the case form)
  • if petitions clerk changes the Party Type, the updated contact fields based on the party selection will display and be blank

Ownership Disclosure Statement

For ONLY party types of Corporation, Partnership (as the Tax Matters Partner), Partnership (as the partner other than the tax matters partner), and Partnership (as the partnership representative under a BBA Regime)

image.png

  • Link to ODS PDF will display
  • On click of the Ownership Disclosure Statement link, the ODS PDF document uploaded with the case form will open in a new tab

Case Info Tab

image.png

  • includes metadata currently under the heading of Case Information,
    • Case Procedure - field is now editable for all internal users
  • Trial location
  • Fee Payment Date
  • Fee Payment ID

IRS Notice Tab

image.png

  • Includes all IRS notice metadata and functionality - as built out in story 588
  • Type of Case/Notice field- is now editable field for all internal users

@ericsorenson ericsorenson added Engineering Engineers have started working on this story. and removed Design Needed Design work will be needed and development work should not start yet labels Feb 28, 2019
@tjcurington tjcurington modified the milestones: Sprint #9, Sprint #10 Mar 7, 2019
@JessicaMarine JessicaMarine removed the Engineering Engineers have started working on this story. label Mar 17, 2019
This was referenced Mar 19, 2019
codyseibert pushed a commit that referenced this issue Jun 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants