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

Case Movement_Non-Blocking Tasks | Assigned To Field Not Displaying Correct User #14214

Closed
1 task
araposo-tistatech opened this issue May 7, 2020 · 2 comments
Closed
1 task

Case Movement_Non-Blocking Tasks | Assigned To Field Not Displaying Correct User #14214

araposo-tistatech opened this issue May 7, 2020 · 2 comments
Assignees
@lomky
Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Team: Echo 🐬 Type: Bug
Milestone
PI4-S2: Amelia Ea...

Comments

@araposo-tistatech
Copy link

araposo-tistatech commented May 7, 2020 •
edited
Loading

Description

The Assigned To field should display the correct user ID on the search cases page

Acceptance criteria

  • The assigned to field on the search cases page displays the correct user assigned to the case

Background/context/resources

During Dogfooding: Assigning a case to an judge (Legacy), reassigning to Burnham assigned case to ID4 instead of CSS_ID29 when searching the case again
Check the dogfooding google doc for screenshots

Technical notes

Reproduce before digging into. Hunter believes that this is due to being unable to assign legacy cases in demo and the lack of an error shown when this occurs. This would leave "Assigned to" unchanged in case search.

Screenshots

image
@araposo-tistatech araposo-tistatech added Product: caseflow-queue Type: Bug Team: Echo 🐬 Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. labels May 7, 2020
@hschallhorn
Copy link
Contributor

Timeboxing to a 2! Could be an issue with the assigned to label or a non refreshed appeal in redux.

@hschallhorn hschallhorn mentioned this issue May 18, 2020
Closed
@lomky lomky self-assigned this May 18, 2020
@hschallhorn hschallhorn added this to the PI4-S2: XXX Sprint milestone May 18, 2020
@lomky
Copy link
Contributor

lomky commented May 20, 2020

Could not replicate. Okay to close @araposo-tistatech ?

ID changes

@lomky lomky closed this as completed May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lomky lomky

Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Team: Echo 🐬 Type: Bug
Projects
None yet
Milestone
PI4-S2: Amelia Earhart Sprint
Development

No branches or pull requests
3 participants
@lomky @hschallhorn @araposo-tistatech