Caseflow: Welcome Gate | Add issues column

[gnakm]

Story

As an attorney, it is hard to distinguish the difference between different appeals of the same Veteran at a glance on the welcome gate page.

We will be adding the Issues as a new column.

AC

• [ ] Add a new header column labeled Issues between Veteran ID and View claims folder and have appropriate Issues matching the appeal. This information is currently labeled "Levels.." in VACOLS
• [ ] Rename View case file to View claims folder
• [ ] Change h2 Work assignments to Cases checked in
• [ ] Remove description under h1 (Reader allows attorneys and judges review and annotate a Veteran’s case file. Reader allows attorneys and judges review and annotate a Veteran’s case file.)
• [ ] If an appeal has multiple issues, have the issues stack on top of each other.

Mock up

Related

2342

https://github.com/department-of-veterans-affairs/appeals-design-research/issues/288

[abbyraskinUSDS]

@cmgiven can you clarify which column in VACOLS we should look at here for program? Is it BFCASEV?

[cmgiven]

It's ISSUES.ISSPROG, which need to be joined on ISSREF.PROG_CODE in order to get the label (ISSREF.PROG_DESC). Alternatively, we could hardcode our preferred labels and skip the join, which may be preferable anyway, as some of the program names are quite long.

[cmgiven]

(Also note that we'll need to allow for the possibility of multiple program areas, probably comma separated? Two program areas is a reasonably common edge case. Three is possible but rare.)

[abbyraskinUSDS]

Thanks!

[gnakm]

@abbyraskin

How about stacking instead of commas? The some of the programs are kind of long and stacking might look cleaner.

I don't think this really effects other views:

[abbyraskinUSDS]

definitely agree @gnakm!

[abbyraskinUSDS]

note to figure out what our preferred hardcoded labels are for all of these - i think that's a better route

[abbyraskinUSDS]

@cmgiven how many program areas are there? could you paste them here when you have a chance? (or direct us to them? tried finding them myself and failed!)

[cmgiven]

   COUNT(*)                            PROG_DESC
1         9                        Loan Guaranty
2         3                            Insurance
3        28            BVA Original Jurisdiction
4       164                              Medical
5       437                              Pension
6         7 NCA Burial benefits (38 CFR Part 38)
7        37  VBA Burial benefits (38 CFR Part 3)
8        26                       Other programs
9     62876                         Compensation
10       19                                 VR&E
11      122                            Education

select count(*), PROG_DESC from ISSUES join (select distinct PROG_CODE, PROG_DESC from ISSREF) on ISSPROG = PROG_CODE where ISSDCLS > date '2017-01-01' and ISSDC in ('1', '3', '4') group by PROG_DESC

[gnakm]

@abbyraskin I wonder if we should make a separate issue for cleaning up program data and check-in with Lara since it effects hearings stuff as well.

[gnakm]

Closing because this has been combined with #2511