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

Litigation Support: Add Admin Actions to CAVC Remand Root Task #15140

Closed
5 tasks
araposo-tistatech opened this issue Sep 2, 2020 · 5 comments
Closed
5 tasks
Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Type: New Development New feature development

Comments

@araposo-tistatech
Copy link

araposo-tistatech commented Sep 2, 2020

User or job story

Job story: When I have a remand case, I should have a limited set of admin actions on the root task before the send 90 day letter task, so that I can get necessary actions done in order as ordered by the Court.

Acceptance criteria

  • Please put this work behind the feature toggle: CAVC_Remand
  • This feature should be accessible to the following user groups: Litigation Support
  • Include screenshot(s) in the Github issue if there are front-end changes
  • POA Clarification is listed on the submit admin actions page - blocks send 90 day letter task
  • Provide Instructions and context for this action appears on the submit admin actions page

Release notes

Out of scope

Designs

Background/context

Technical notes

Other notes

Resources/other links

@araposo-tistatech araposo-tistatech added Product: caseflow-queue Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Type: New Development New feature development labels Sep 2, 2020
@araposo-tistatech
Copy link
Author

@geronimoramos @mbaenatan I believe this is the ticket that is causing a bit of confusion for me. Do we really need a limited set of admin actions before the send 90 day letter task and then a different set after the 90 day letter task was sent? Can't we just have all of them on one task?

@geronimoramos
Copy link

@geronimoramos @mbaenatan I believe this is the ticket that is causing a bit of confusion for me. Do we really need a limited set of admin actions before the send 90 day letter task and then a different set after the 90 day letter task was sent? Can't we just have all of them on one task?

The intention for the limited set of admin actions is to help reduce errors and potential confusion in the event they select the wrong admin action. Also, since these users are new to Caseflow, I think having all the admin actions available to them can be overwhelming/misleading. Curious to hear @mbaenatan thoughts!

@mbaenatan
Copy link

@araposo-tistatech Let's go with the full list of admin actions and have the full list for both before and after the 90-day letter is sent. We will confirm this full list on Thursday 9/17.
You bring up a good point @geronimoramos around confusion and 1st time Caseflow users but since we've "co-created" this with them it shouldn't be too foreign. I'd rather they have a learning curve and have the all the actions they need rather than getting stuck and holding up the process

@geronimoramos
Copy link

Agreed. I like the idea of using what exists and deducting from there if necessary. I think specifics in the training materials will be helpful for the users.

@araposo-tistatech
Copy link
Author

duplicate of #15286, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Stakeholder: BVA Functionality associated with the Board of Veterans' Appeals workflows/feature requests Team: Echo 🐬 Type: New Development New feature development
Projects
None yet
Development

No branches or pull requests

3 participants