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

Create Dispatch Establish Claims controller schema to catch mismatch Special Issues #14659

Closed
1 task
lomky opened this issue Jul 8, 2020 · 1 comment
Closed
1 task

Create Dispatch Establish Claims controller schema to catch mismatch Special Issues #14659

lomky opened this issue Jul 8, 2020 · 1 comment
Labels
Priority: Low Reported issue, not a blocker. "Last in" priority for new work. Product: caseflow-dispatch Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Type: Enhancement Enhancement to an existing feature
Milestone
PI5-S1: Social Se...

Comments

@lomky
Copy link
Contributor

lomky commented Jul 8, 2020

Description

Read through Yang's documentation here and create a controller-schema for the Dispatch Establish Claims controller update_appeal route.

Acceptance criteria

  • Ensure existing tests pass

Background/context/resources

Followup to #14018 - Caseflow Dispatch front end and back end rely on two sets of Special Issues, so implementing this schema puts some checks in place. Right now mismatching ids are silently discarded. With the schema they will produce a warning

Technical notes
@lomky lomky added Product: caseflow-dispatch Type: Enhancement Enhancement to an existing feature Team: Echo 🐬 Priority: Low Reported issue, not a blocker. "Last in" priority for new work. labels Jul 8, 2020
@lomky lomky changed the title Create Dispatch Establish Claims controller to catch mismatch Special Issues Create Dispatch Establish Claims controller schema to catch mismatch Special Issues Jul 9, 2020
@ajspotts
Copy link
Contributor

ajspotts commented Jul 9, 2020

what is this chart?

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

Why 1?

  • God documentation on how to do

Why 2?

  • Have never done it before!

Why 3?

  • Well documented and straight forward, but some spin up time for folks who haven't seen the schema work

Why 5?

  • Ramp-up

@hschallhorn hschallhorn added the Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests label Jul 9, 2020
@hschallhorn hschallhorn mentioned this issue Jul 13, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: Low Reported issue, not a blocker. "Last in" priority for new work. Product: caseflow-dispatch Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Type: Enhancement Enhancement to an existing feature
Projects
None yet
Milestone
PI5-S1: Social Security Sprint
Development

No branches or pull requests
4 participants
@lomky @ajspotts @hschallhorn @ThorntonMatthew