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

Motion to Vacate | Set Up Container Component for MTV Workflow #13318

Closed
3 tasks
jcq opened this issue Jan 31, 2020 · 0 comments
Closed
3 tasks

Motion to Vacate | Set Up Container Component for MTV Workflow #13318

jcq opened this issue Jan 31, 2020 · 0 comments
Assignees
Labels
Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Foxtrot 🦊

Comments

@jcq
Copy link
Contributor

jcq commented Jan 31, 2020

Description

The workflow for handling of post decision motions (MTV) is intended to be done in a largely similar way to the normal handling of judge and attorney tasks, but with a few key differences. Various UI and copy changes are present, and it is desired to use different routes. Due to these and the need for different views/workflows based on disposition, appeal stream type, etc, it makes sense to set up a new parent container component to handle the data/logic on which the child views will rely.

Background/context/resources

This will wrap/enable the items from these other tickets:

Technical notes

The data layer could be handled in Redux (and certain bits such as the appeal stream type, etc will be pulled from there), but the handling of the view logic and user inputs might be better handled via the React Context API. That decision can be left to the engineer.

Acceptance Criteria

  • Create routing for various MTV items
  • Pull in required data from Redux store (appeal, including stream ID and stream type)
  • Set up data layer to be able to provide all necessary data to children as props
@jcq jcq added Team: Foxtrot 🦊 Stakeholder: OIT New requirements gathered by Geoffrey/Office of Information & Technology Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests labels Jan 31, 2020
@jcq jcq changed the title Set Up Container Component for MTV Workflow MTV | Set Up Container Component for MTV Workflow Jan 31, 2020
@msj0nes msj0nes removed the Stakeholder: OIT New requirements gathered by Geoffrey/Office of Information & Technology label Feb 2, 2020
@jcq jcq self-assigned this Feb 3, 2020
@msj0nes msj0nes changed the title MTV | Set Up Container Component for MTV Workflow Motion to Vacate | Set Up Container Component for MTV Workflow Feb 5, 2020
va-bot pushed a commit that referenced this issue Feb 6, 2020
Connects #13318

### Description
This does multiple things:
- refactors `QueueApp` to break out MTV routes into their own file
- creates MotionToVacateContext for data handling as part of MTV checkout flow
- creates MotionToVacateFlowContainer that will serve as a container for the MTV checkout flows

### Acceptance Criteria
- [ ] Code compiles correctly
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Foxtrot 🦊
Projects
None yet
Development

No branches or pull requests

3 participants