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

New Organization: CAVC Litigation Support Team #15278

Closed
3 tasks
araposo-tistatech opened this issue Sep 21, 2020 · 5 comments · Fixed by #15443
Closed
3 tasks

New Organization: CAVC Litigation Support Team #15278

araposo-tistatech opened this issue Sep 21, 2020 · 5 comments · Fixed by #15443
Assignees
Labels
Eng: Beginner Friendly Good tickets for new team members 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 21, 2020

User or job story

User story: As a Litigation Support team member who only works on CAVC cases, I need my own separate queue in Caseflow, so that I do not work or see any tasks that do not pertain to CAVC.

Acceptance criteria

Background/context

Not all users in the Litigation Support team work all tasks. As the team that only works CAVC cases has never migrated to Caseflow we will want to include them as a new organization so they are not inadvertently assigned tasks they are not authorized to work or vice versa.

Technical notes

Other notes

image

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. labels Sep 21, 2020
@araposo-tistatech
Copy link
Author

@geronimoramos created this ticket, feel free to update if the team name is incorrect.

@hschallhorn
Copy link
Contributor

Be sure to call CavcLitigationSupportTeam.singleton in prod after deployed to create the team!

@hschallhorn hschallhorn added the Type: New Development New feature development label Sep 24, 2020
@yoomlam
Copy link
Contributor

yoomlam commented Oct 1, 2020

what is this chart?

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

Why 1?

  • Create a new empty org with no tasks/actions? ok

Why 2?

  • Verification in prod

@yoomlam yoomlam self-assigned this Oct 16, 2020
@yoomlam yoomlam added the Eng: Beginner Friendly Good tickets for new team members label Oct 16, 2020
@lomky lomky added this to the PI5-S6: XXX Sprint milestone Oct 19, 2020
@yoomlam
Copy link
Contributor

yoomlam commented Oct 19, 2020

Each org/team has an associated url. What should the url for this new team be? My initial guess is cavc-lit-support

=> #<CavcLitigationSupport:0x00007fdc7803a9d8
 id: 30,
 accepts_priority_pushed_cases: nil,
 created_at: Mon, 19 Oct 2020 14:07:24 UTC +00:00,
 name: "CAVC Litigation Support",
 participant_id: nil,
 role: nil,
 status: "active",
 status_updated_at: nil,
 type: "CavcLitigationSupport",
 updated_at: Mon, 19 Oct 2020 14:07:24 UTC +00:00,
 url: "cavc-lit-support">

@yoomlam
Copy link
Contributor

yoomlam commented Oct 19, 2020

va-bot pushed a commit that referenced this issue Oct 19, 2020
Resolves #15278 

### Description
Added a new organization called "CAVC Litigation Support" for the new team that handles CAVC-related tasks.

### Acceptance Criteria
- [ ] Include screenshot(s) in the Github issue if there are front-end changes, showing new org
- [ ] Update documentation: https://github.com/department-of-veterans-affairs/caseflow/wiki/Organizations
- [ ] New organization added to Caseflow for CAVC Litigation Support Team
- [ ] Reminder to self: #15278 (comment)

### Testing Plan
1. Create team in dev environment and check its information
```ruby
CavcLitigationSupport.singleton
```
2. Check the UI: http://localhost:3000/organizations/cavc-lit-support/users
3. Add and remove users in the UI and check in Rails console: 
```ruby
team=CavcLitigationSupport.singleton
team.users
````

Review new bullet for CavcLitigationSupport in https://github.com/department-of-veterans-affairs/caseflow/wiki/Organizations#existing-organizations


### User Facing Changes
 - [ ] Screenshots of UI changes added to PR & Original Issue


 BEFORE|AFTER
 ---|---
(none) | ![image](https://user-images.githubusercontent.com/55255674/96464218-2c1dbd80-11ed-11eb-9beb-fe2fad4a129f.png)
(doesn't have CAVC Lit Support team) | ![image](https://user-images.githubusercontent.com/55255674/96464356-53748a80-11ed-11eb-83ab-52098a8b5bc8.png)


### Code Documentation Updates
- [ ] Add or update code comments at the top of the class, module, and/or component.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Eng: Beginner Friendly Good tickets for new team members 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

Successfully merging a pull request may close this issue.

4 participants