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

Validate document_id when checking if a decision has been written for a case #13688

Closed
1 task
hschallhorn opened this issue Mar 12, 2020 · 1 comment · Fixed by #13831
Closed
1 task

Validate document_id when checking if a decision has been written for a case #13688

hschallhorn opened this issue Mar 12, 2020 · 1 comment · Fixed by #13831
Assignees
Labels
Feature: generic-queue Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Team: Echo 🐬 Type: Bug User: AVLJ Acting Veterans Law Judge

Comments

@hschallhorn
Copy link
Contributor

hschallhorn commented Mar 12, 2020

User story

As an AVLJ, I need to see attorney actions on legacy cases assigned to me, so that I can draft decisions. As of right now, if the document id on the appeals associated decass record is anything other than nil, acting judges are shown judge actions. On occasion, this value will read "NONE". We should instead validate that the document id is valid, not just that it exists.

Acceptance criteria

Out of scope

Further work to better determine what actions to show an AVLJ will be done. This issue is to only solve the issue that arose from invalid document ids.

Background/context

Allow AVLJs to be assigned legacy cases #11971
Allow AVLJs to perform judge tasks on legacy appeals #11977
Use the presence of a decision doc id to determine if a case has already gone to an attorney #13530

Technical notes

We already do validation of document ids on attorney checkout here. This could be reused.

@hschallhorn hschallhorn added Product: caseflow-queue Type: Bug Feature: generic-queue Team: Echo 🐬 Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. User: AVLJ Acting Veterans Law Judge labels Mar 12, 2020
@lomky
Copy link
Contributor

lomky commented Mar 13, 2020

what is this chart?

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

Based on when Doc ids are pulled from DAS, which might not be done in Caseflow, so its not validated by us.
Only affects legacy appeals. Where we pull in cases from vacols for a users legacy queue.

Estimating at a 3.

Might be simple as the location is well known, just have to update the value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: generic-queue Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Team: Echo 🐬 Type: Bug User: AVLJ Acting Veterans Law Judge
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants