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

CAVC Remand: Update Auto-Distribution Criteria for Priority AMA Cases #14958

Closed
4 tasks
araposo-tistatech opened this issue Aug 13, 2020 · 3 comments
Closed
4 tasks
Labels
Feature: auto-case-distribution Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Team: Echo 🐬 Type: Enhancement Enhancement to an existing feature

Comments

@araposo-tistatech
Copy link

araposo-tistatech commented Aug 13, 2020

User or job story

Job story: When a Litigation Support user completes the intake of a CAVC remand the CAVC Remanded case should be auto-distributed to VLJs via the Auto-Distribution Job, so that the VLJ can work these cases before legacy hearing & general population cases.

Acceptance criteria

  • This feature should be accessible to the following user groups: VLJs
  • AMA CAVC Remands in-taken by the Litigation Support are included in the auto-distribution job for priority cases
  • AMA CAVC Remands in-taken by the Litigation Support are included in the requested auto-distribution for priority cases
  • Pare down code reuse with a refactor if possible

Background/context

Legacy CAVC remanded cases are already incorporated into the algorithm, this ticket is to ensure AMA CAVC remands intaken by the Litigation Support team are incorporated as well.

Appeal Priority Order:
CAVC AOD
AOD
CAVC

Technical notes

Where we determine what case is priority for ama appeals distributions

def priority
join_aod_motions
.where("advance_on_docket_motions.created_at > appeals.established_at")
.where("advance_on_docket_motions.granted = ?", true)
.or(join_aod_motions
.where("people.date_of_birth <= ?", 75.years.ago))
.group("appeals.id")
end

Other notes

Resources/other links

@araposo-tistatech araposo-tistatech added Type: Enhancement Enhancement to an existing feature Product: caseflow-queue Feature: auto-case-distribution Team: Echo 🐬 Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. labels Aug 13, 2020
@araposo-tistatech
Copy link
Author

@hschallhorn should I create duplicate tickets for this one to incorporate MDR, Reversals, & Dismissals in the future or do you think this one ticket will capture even future work?

@hschallhorn
Copy link
Contributor

Good question! I think it depends on what we decide on for appeal stream type naming. If we plan on calling all "Court Remand" (as we do with legacy appeals) or something similar, then they will all be captured in this work. If we decide MDR, Reversals, & Dismissals need to have their own stream type, then we will need tickets for each.

@hschallhorn hschallhorn changed the title CAVC Remand: Update Auto-Distribution Job for Priority Cases CAVC Remand: Update Auto-Distribution Criteria for Priority Cases Sep 24, 2020
@hschallhorn hschallhorn changed the title CAVC Remand: Update Auto-Distribution Criteria for Priority Cases CAVC Remand: Update Auto-Distribution Criteria for Priority AMA Cases Nov 12, 2020
@hschallhorn
Copy link
Contributor

what is this chart?

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

Should update requested ACD test, priority push job test, and distribution seeds.

Why 2?

  • Sounds pretty clear...
  • Simple update to the priority scope for acd

Why 3?

  • ...but ACD
  • ACD test updates
  • Seconded ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: auto-case-distribution Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Team: Echo 🐬 Type: Enhancement Enhancement to an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants