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

Add user column to team queue table #8241

Closed
lpciferri opened this issue Dec 12, 2018 · 4 comments
Closed

Add user column to team queue table #8241

lpciferri opened this issue Dec 12, 2018 · 4 comments

Comments

@lpciferri
Copy link

lpciferri commented Dec 12, 2018

We want to add the user column to team queues so supervisors and team members know who is working on tasks.

This is especially important if teams decide to have users self-assign work (like the Hearings Management Branch has suggested), or reassign work when users are out on leave.

AC

  • User column exists on team queue, Assigned and Completed tab

Mocks

User column on "Assigned" tab

colocated-table-team-cases-768

Considerations and implications:

  • to add this column (and especially to suit our narrowest browser width specifications), I removed "Type" column (Original, CAVC, Reconsideration, etc). [now outdated]
    [UPDATE]: I've reintroduced type column and omitted veteran documents column.

Open questions [all resolved as of 01/16/19]

  • is it easier to add user column to all tabs, even though the Unassigned tab doesn't have assigned users?
    - Sneha: Adding this column requires sacrificing another important column that may be useful when viewing team cases. I think we should limit adding this column only to assigned and completed tabs.
  • Is it okay to remove "type" column? If not, which other column would we want to remove in order to add the "assigned to" column?
@sneha-pai
Copy link
Contributor

@laurjpeterson can you please have a look at the proposed mock, and questions around if we include this column, which other column do we not show?

@lpciferri
Copy link
Author

thank you @sneha-pai!

is it easier to add user column to all tabs, even though the Unassigned tab doesn't have assigned users?

  • Sneha: Adding this column requires sacrificing another important column that may be useful when viewing team cases. I think we should limit adding this column only to assigned and completed tabs.
  • Ok

Is it okay to remove "type" column? If not, which other column would we want to remove in order to add the "assigned to" column?

  • I think I'd prefer to remove the link to Reader, since users can navigate to Reader from Case Details
  • Type is important for AOD, CAVC, etc. for legacy cases.
  • I'd love @MeredithStewart @Chingujo @laurenrussell 's eyes on this too, for their thoughts on this w/r/t hearing branch

@laurenrussell
Copy link

@laurjpeterson I would agree, in that Type is important to stay on track when filling the docket.

@sneha-pai sneha-pai mentioned this issue Dec 18, 2018
19 tasks
@allyceh allyceh self-assigned this Jan 7, 2019
@lpciferri
Copy link
Author

Note: VLJ support staff would benefit from the user column on the team queue soon as well, so they can easily know when they need to reassign cases from user to user. cc: @sneha-pai @mdbenjam

@ghost ghost assigned joeyyang Jan 25, 2019
@ghost ghost added the In-Progress label Jan 25, 2019
@ghost ghost removed the In-Progress label Jan 31, 2019
va-bot pushed a commit that referenced this issue Jan 31, 2019
…plete tabs) (#8947)

Resolves #8241
/cc @laurjpeterson 

### Description
Adds an 'assigned to' column to organization queue view (assigned and complete tabs).

<img width="959" alt="screenshot 2019-01-28 16 32 36" src="https://user-images.githubusercontent.com/2928395/51867879-99533600-231a-11e9-9d99-329220dc094e.png">
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants