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

Allow judges to send admin actions to VLJ support for Legacy appeals #8757

Closed
3 tasks
lowellrex opened this issue Jan 16, 2019 · 2 comments
Closed
3 tasks

Allow judges to send admin actions to VLJ support for Legacy appeals #8757

lowellrex opened this issue Jan 16, 2019 · 2 comments
Labels
Feature: co-located Feature: generic-queue Product: caseflow-queue Team: Foxtrot 🦊 User: Judge

Comments

@lowellrex
Copy link
Contributor

lowellrex commented Jan 16, 2019 •
edited
Loading

#8608 enabled judges to send admin actions directly to VLJ support for AMA appeals. This ticket exists to allow judges to send admin actions to VLJ support for Legacy appeals.

Acceptance criteria

  • Judges have the option to Add admin action from the Case details page for Legacy appeals, currently active tasks component, Actions dropdown
  • When judges click Add admin action for a Legacy appeal, they navigate to the add admin action page (same behavior as attorneys)
  • Location code updates in VACOLS as expected.
@lowellrex lowellrex mentioned this issue Jan 16, 2019
Merged
@lpciferri lpciferri mentioned this issue Feb 6, 2019
Closed
4 tasks
@lpciferri
Copy link

@lowellrex - i think we can actually close this. i sat with a judge today (Thomas O'Shay) and he had the add admin action option!

@lowellrex
Copy link
Contributor Author

Whoops! You're right! Good call!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature: co-located Feature: generic-queue Product: caseflow-queue Team: Foxtrot 🦊 User: Judge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lpciferri @lowellrex