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

Fix missing Legacy cases after case is signed #13872

Closed
1 task
araposo-tistatech opened this issue Apr 2, 2020 · 4 comments
Closed
1 task

Fix missing Legacy cases after case is signed #13872

araposo-tistatech opened this issue Apr 2, 2020 · 4 comments
Assignees
Labels
Priority: High Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work. Product: caseflow-queue Source: Bat Team Team: Echo 🐬 Type: Bug User: Judge

Comments

@araposo-tistatech
Copy link

Description

After a judge signs a case, when they return to their queue view, legacy cases are no longer listed until the page is reloaded/refreshed.

Acceptance criteria

  • Legacy cases are present (without a manual page refresh) in the judges queue view after the judge signs a case

Background/context/resources

Per VLJ User:
"When I finish signing a case, Caseflow loads a page that shows the cases I have available pending my signature. Lately, that list only shows AMA appeals and not Legacy appeals. If I refresh the list, then the list will include all (AMA and Legacy) appeals. Other Judges have experienced the same issue so I do not think it is unique to me."

Technical notes

Possibly related to #13664

@araposo-tistatech araposo-tistatech added Team: Echo 🐬 Priority: High Escalations from Support, blocking issue/NO workaround, or "first in" priority for new work. User: Judge Type: Bug Product: caseflow-queue Source: Bat Team labels Apr 2, 2020
@jjohni
Copy link

jjohni commented Apr 3, 2020

YourIT Ticket Number Date Ticket Created Case Details URL
INC0000000 00/00/00 Add case details page URL here
INC10192233 04/03/2020 On the case details page of there queue product
INC10176192 04/02/2020 On the case details page of there queue product
INC10177256 04/02/2020 On the case details page of there queue product
INC10169579 04/01/2020 On the case details page of there queue product

@ajspotts
Copy link
Contributor

ajspotts commented Apr 9, 2020

what is this chart?

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

Why 2?

  • Wishful thinking? May be a small code change.

Why 3?

  • State management can be complicated in our app

@hschallhorn
Copy link
Contributor

😕 Having a hard time reproducing this again. Steps I followed:

  1. Log in as bvaaabshire
  2. Go to their queue
  3. Click a legacy case
  4. Select ready for dispatch
  5. Continue through checkout
  6. Ensure all legacy cases appear in queue

Also tested searching for a case so that tasks were not loaded through queue before dispatching a case. Looks like everything loads correctly.

After sending to dispatch, before refresh After refresh
Screen Shot 2020-09-29 at 11 16 04 AM Screen Shot 2020-09-29 at 11 16 10 AM

Thoughts:
This may have been resolved by #14252. One of the changes was that every time queue is loaded, we pull tasks from the back end.

@hschallhorn
Copy link
Contributor

Fixed in #14252

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-queue Source: Bat Team Team: Echo 🐬 Type: Bug User: Judge
Projects
None yet
Development

No branches or pull requests

4 participants