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

Dispatch & Special Issues Investigation #14433

Closed
1 task done
lomky opened this issue May 29, 2020 · 1 comment
Closed
1 task done

Dispatch & Special Issues Investigation #14433

lomky opened this issue May 29, 2020 · 1 comment
Assignees
Labels
Priority: High Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work. Product: caseflow-dispatch Product: caseflow-queue Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Type: Investigation

Comments

@lomky
Copy link
Contributor

lomky commented May 29, 2020

While continuing to implement the New Contentions, #13423, we've discovered some unexpected behavior in how Queue and Dispatch are interacting differently with Special Issues (SI). To proceed, we need to answer several questions so we can clarify the path forward.

AC:

  • Essential questions are answered & documented in a wiki

Essential Questions:

  • How do cases get to "ready for dispatch", for both AMA and Legacy cases
    • if feasible, create some seed data for both with already selected SIs
  • Does Dispatch understand that the SpecialIssuesList object exists
  • How does Dispatch interact with LegacyAppeals on-object SpecialIssues
  • How does the SpecialIssues information leave caseflow, for AMA and for Legacy
  • Does Dispatch handle all Legacy appeals, or just a subject?
  • Do users see the Special Issues page in production on AMA?

Helpful Additional Information

  • Why does Dispatch offer all Special Issues on AMA appeals?
  • When can we expect that a legacy case is "Done" in Caseflow, in the happy path?
@lomky lomky added Product: caseflow-dispatch Type: Investigation Product: caseflow-queue Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Priority: High Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work. labels May 29, 2020
@yoomlam
Copy link
Contributor

yoomlam commented May 29, 2020

Prior comments: #13736 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: High Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work. Product: caseflow-dispatch Product: caseflow-queue Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Type: Investigation
Projects
None yet
Development

No branches or pull requests

3 participants