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.

Sign up for GitHub

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

Jump to bottom

CAVC Remand: Litigation Support Form (Front End) #14795

Closed
14 tasks
araposo-tistatech opened this issue Jul 29, 2020 · 5 comments · Fixed by #15597
Closed
14 tasks

CAVC Remand: Litigation Support Form (Front End) #14795

araposo-tistatech opened this issue Jul 29, 2020 · 5 comments · Fixed by #15597
Assignees
@ajspotts
Labels
Priority: High Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work. Product: caseflow-queue Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Type: New Development New feature development
Milestone
PI5-S7: Veterans ...

Comments

@araposo-tistatech
Copy link

araposo-tistatech commented Jul 29, 2020 •
edited by hschallhorn
Loading

User or job story

Job story: A a Litigation Support user I need the ability to start and add data for a CAVC Remand to Caseflow so that a new appeal stream can be created and decided by the Board.

Acceptance criteria

  • Please put this work behind the feature toggle: CAVC_Remand
  • This feature should be accessible to the following user groups: CAVC Litigation Support
  • Include screenshot(s) in the Github issue if there are front-end changes
  • Start CAVC Remand Documentation to describe what cavc remand features caseflow supports (to be updated as more cavc functionality is added)
  • Add CAVC Court Order Button to Case Details page of a Dispatched/Completed appeal that presents the form in a new top section
  • CAVC Litigation Support user can select a cavc judge from a prepopulated dropdown
  • CAVC Litigation Support user can add receipt date to the form
  • CAVC Litigation Support user can designate the type of remand (JMR, JMPR) on the form
  • CAVC Litigation Support user can enter dates for
    • Court decision
    • Judgement
    • Mandate
  • Confirmation Modal appears with the following copy when the form is completed & submitted (confirmation message may not be true at the end of this ticket until new appeal stream and 90 day letter task portions have been implemented):
    - You have successfully created a CAVC Remand case
    This has generated a Send 90 Day Letter task in your team's queue

Testing

  • Ensure users can copy and paste values from the cavc website without modifying data (see here for how to get to the publicly available records)

Release notes

The Litigation Support Organization now has the ability to intake JMR & JMPR CAVC remanded cases for previously dispatched appeals.

Designs

➡️ UI designs and flow ⬅️

Case Details without task v2

Technical notes

Other notes

Resources/other links

https://docs.google.com/document/d/1-EzNBC83BjyiRhtBl_s5rrf2Qejp4b7NHsVC7JW4FzA/edit#

How to view a CAVC public docket case
@araposo-tistatech araposo-tistatech added Product: caseflow-queue Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Type: New Development New feature development labels Jul 29, 2020
@lpciferri lpciferri mentioned this issue Jul 29, 2020
Closed
12 tasks
@araposo-tistatech araposo-tistatech changed the title CAVC Remand: Litigation Support Workflow CAVC Remand: Litigation Support Workflow (Front End) Jul 29, 2020
@araposo-tistatech araposo-tistatech mentioned this issue Jul 29, 2020
Closed
5 tasks
@araposo-tistatech araposo-tistatech changed the title CAVC Remand: Litigation Support Workflow (Front End) CAVC Remand: Litigation Support Form (Front End) Sep 11, 2020
@araposo-tistatech
Copy link
Author

@geronimoramos can we add the designs for the form here limited to what is needed for adding a JMR & JMPR? Also, please add any necessary AC's that I may have missed.

@araposo-tistatech araposo-tistatech added Priority: High Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work. and removed Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. labels Sep 14, 2020
@geronimoramos
Copy link

Added in the UI designs/flow with some items in review:

  1. pre-populating CAVC judges' names (awaiting confirmation from lit support)
  2. Potentially getting rid of the judgment date input field (awaiting confirmation from lit support)

@geronimoramos
Copy link

box-shadow: 0px 2px 8px rgba(0, 0, 0, 0.15); for the Post Dispatch actions section

@hschallhorn hschallhorn mentioned this issue Sep 21, 2020
Closed
3 tasks
@araposo-tistatech araposo-tistatech mentioned this issue Sep 21, 2020
Closed
@hschallhorn
Copy link
Contributor

what is this chart?

1 | 
2 | 
3 | ||||||
5 | |||
8 |

Why 3?

  • New ui
  • No tricky interactions between fields, simple data entry

Why 5?

  • Rpecs for UI testing

@hschallhorn hschallhorn added this to the PI5-S7: XXX Sprint milestone Nov 2, 2020
@geronimoramos
Copy link

See here how to get to view a public docket case on the CAVC website https://www.loom.com/share/cdab86399e524632a1ba3e8ae6b3a12e

@ajspotts ajspotts self-assigned this Nov 6, 2020
@ajspotts ajspotts mentioned this issue Nov 10, 2020
Merged
22 tasks
@hschallhorn hschallhorn mentioned this issue Dec 7, 2020
Closed
2 tasks
va-bot pushed a commit that referenced this issue Dec 7, 2020
@ajspotts
CAVC Remand: Litigation Support Form (Front End) (#15597)
7b4d8e0 
Resolves #14795. Resolves CASEFLOW-65

### Description
Creates a new Post-dispatch actions area on the Case Details page which houses the Add Cavc Remand option.  This option is only available to member of the `CavcLitigationSupport` org and is also hidden behind the `cavc_remand` feature toggle.

Also creates the new Cavc Intake Form, which in conjunction with the work completed in #15351 and #15469 will allow Cavc litigation users to create a new Cavc appeal stream.

### Acceptance Criteria
- [x] "+Add Cavc remand" button is behind `cavc_remand` feature toggle
- [x] Only Cavc Litigation Support users can see the button
- [ ] Start CAVC Remand Documentation to describe what cavc remand features caseflow supports (to be updated as more cavc functionality is added)
- [x] Add CAVC Court Order Button to Case Details page of a Dispatched/Completed appeal that presents the form in a new top section
- [x] Cavc Litigation Support user can add the following required fields:
  - [ ] court docket number
  - [ ] Attorney representation
  - [ ] Cavc judge
  - [ ] Decision type (remand, death dismissal, etc)
  - [ ] type of remand (JMR, JMPR) on the form (only if remand)
  - [ ] Court decision date
  - [ ] Judgement date
  - [ ] Mandate date
  - [ ] issues required to be decided on in the new appeal stream
  - [ ] instructions
- [x] Confirmation alert appears with the following copy when the form is completed & submitted: 
        "You have successfully created a CAVC Remand case
         This has generated a Send 90 Day Letter task in your team's queue"
- [ ] Ensure users can copy and paste values from the cavc website without modifying data (see [here](#14795 (comment)) for how to get to the publicly available records)

### Testing Plan
1. Enable cavc_remand feature toggle
1. Find a dispatched appeal (search for vet 500000000)
1. Click "+ Add CAVC Remand"
1. Press submit and confirm validations
1. Confirm selecting "Death Dismissal" hides remand subtype
1. Fill out the form, keeping JMR selected
1. Deselect an issue
1. Press submit and confirm error message
1. Select all issues and press submit.
1. Confirm success message on case details of new appeal
1. Confirm case details shows correct information entered

### User Facing Changes
 - [ ] Screenshots of UI changes added to PR & Original Issue

Workflow|UI
 ---|---
New button|<img width="1447" alt="Screen Shot 2020-11-17 at 4 29 21 PM" src="https://user-images.githubusercontent.com/45575454/99457467-07565c00-28f9-11eb-8185-a590650e414d.png">
Validations|<img width="917" alt="Screen Shot 2020-11-17 at 1 57 50 PM" src="https://user-images.githubusercontent.com/45575454/99457433-f60d4f80-28f8-11eb-9250-3f7ecd7dc8ea.png"><img width="915" alt="Screen Shot 2020-11-17 at 1 57 58 PM" src="https://user-images.githubusercontent.com/45575454/99457438-f86fa980-28f8-11eb-9a2c-fa2ebe3b2bb0.png">
Back end error|<img width="818" alt="Screen Shot 2020-11-17 at 3 54 27 PM" src="https://user-images.githubusercontent.com/45575454/99457452-00c7e480-28f9-11eb-9489-87eefd9796a6.png">
Success Alert and new appeal|<img width="1115" alt="Screen Shot 2020-11-17 at 5 21 14 PM" src="https://user-images.githubusercontent.com/45575454/99457662-53090580-28f9-11eb-89fa-02b65183df65.png">

### Code Documentation Updates
- [ ] Add or update code comments at the top of the class, module, and/or component.

### Storybook Story
*For Frontend (Presentationa) Components*
* [x] Add a [Storybook](https://github.com/department-of-veterans-affairs/caseflow/wiki/Documenting-React-Components-with-Storybook) file alongside the component file (e.g. create `MyComponent.stories.js` alongside `MyComponent.jsx`)
* [x] Give it a title that reflects the component's location within the overall Caseflow hierarchy
* [x] Write a separate story (within the same file) for each discrete variation of the component
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ajspotts ajspotts

Labels
Priority: High Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work. Product: caseflow-queue Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Type: New Development New feature development
Projects
None yet
Milestone
PI5-S7: Veterans Day Sprint
Development

Successfully merging a pull request may close this issue.

CAVC Remand: Litigation Support Form (Front End) department-of-veterans-affairs/caseflow
4 participants
@ajspotts @hschallhorn @geronimoramos @araposo-tistatech