The main nav buttons overflow the container on both prod and dev (different behaviors on each):

Dev:

Prod:

Possible solutions:

• Change breakpoint
• Put some of the options within a dropdown (e.g. Create Groups + Browse Groups + My Groups = Groups)... or something.
• Wrap nav (prob ugly)

• Checkout develop
• yarn install
• sail up
• yarn run hot

-> result: app looks right

• yarn upgrade vue
• yarn upgrade vue-template-compiler

-> result: app looks wrong, lots of console errors about things already being declared.

Small nit: on the Browse Groups page to me the Groups breadcrumb heading reads as an input element with "Groups" as placeholder text. And the Search input reads as a button:

I usually click a few times before my brain engages and realizes what's going on...

Maybe moving the search input to its own line to give it more space for input?

As a group admin, I want to plan course sections and enrollments (similar to the persons table).

Also on the courses table, unpublished courses should appear different from published courses (again, similar to persons table). Right now, unpublished look the same as published.

Within an individual User view, a user (with appropriate permissions) should be able to edit or add leaves. Edit Leaves functionality should be similar to the Edit Group, in that clicking on the Edit button allows an editor to add or update listed leaves for the user.

A leave has:

• description, which can be empty
• type, which is selected from a dropdown. Only defined types are allowed. Editor cannot create a new type, like some of the combobox stuff elsewhere in the app.
• status, again a well defined type like confirmed, pending, cancelled
• start_date, which must be defined
• end_date, again which must be defined. The UI should check that the end_date is after the start_date of course

Other Notes:

• if a user api response has user.leaves defined, then the current user can edit the leaves. For example, if I'm a current user and browsing the user User123. If the server returns a defined user.leaves value on the User123 object, I have permissions to edit the leaves for User123.
• when viewing leaves, a user can check a View Previous checkbox, which will show previous leaves
• it may make sense to add an endpoint for the leaves resources
• user may have multiple overlapping leaves. For example, one leave might be a single course release and overlap the dates of a different leave.

As a leave editor, I want to add a link to one or more artifacts (like a document) to a given leave so that I have a record of information related to the leave.

This is similar to the ability to add link artifacts to groups.

https://bluesheet.cla.umn.edu/group/91

Chart view would be a bit more helpful if it showed roles in addition to names:

(shouldn't show the autofill suggestion)

As a course scheduler, I want to "pencil in" instructor or course information for future terms, so that I can plan upcoming semesters.

For example, if I'm an I'm viewing the scheduling report by course/term, I want to drag and drop a possible instructor from a list onto a particular course/term as a tentative instructor.

Similarly when viewing by instructor/term, I want to drag and drop possible courses onto the instructor/term cell.

One idea for functionality is toggling an "edit mode" which would open up a panel of possible courses or instructors on the right, which users could drag to the table.

Questions:

• How should we persist this data?
• How should it be reconciled once the data is no longer tentative?
• Who should have permissions to edit? (Is it the same as schedule viewers?)
• Who should have permission to view the tentative items (I imagine seeing a work-in-progress schedule could get spicy with faculty who will have their own wants/needs).
• Do we need to allow admins to pencil in new courses (or instructors or TA's)?

When downloading the list of LATIS DCs (https://bluesheet.cla.umn.edu/role/17), I expected a list of departments with their associated DC names and emails. Instead the list gives just the information about the DC person repeatedly, presumedly one row for each department.

The top of the Fiscal Report page refers to a button that isn't present anymore.

• departments in rows
• semsters in columns
• leave count in each cell

Admins expressed concern that "Scheduling Report" implies that it changes peoplesoft schedule.

Related #87

As a scheduling report user, I want to see assistantship history for TA's by person/term and course/term (see: #71) similar to how I currently see I can see an instructor's teaching history.

This maybe is a toggle or a select dropdown where the report viewer can choose the role. (Currently, we're thinking of the TA view and the instructor view as mutually exclusive – users wouldn't need to see both at the same time).

Vue3 (on dev):

Prod:

• in the roles. dropdown, hide official roles when not we're working on a list/committee/etc

We have some v-tour stuff sprinkled into our vuejs. We should decide how we feel about tours and either update it or strip it

On the groups page, more than once I've found myself clicking on the gray box to enter text.

The gray "Groups" bar reads as an input with placeholder of groups to me and the search input reads as a search button:

Perhaps making the search input larger and stacking them? Or maybe removing the gray box around the breadcrumbs would help?

On vue3 / dev site:

• Edit Group
• Check "show unit" box
• Save group
• Refresh page
• click "edit group"

-> "Show unit" isn't checked, but the unit is drawing properly. Just not binding correctly

• if a user is flagged as group admin, they should have perms to all child groups
• if a user is flagged group admin, they should be able to create subgroups

Assume this is because of the merge issue - some reports are missing on dev

Looks like some empty list items are rendering for some reason:

IE, don't draw the underscore in "COURSE_BUYOUT"

dev:

Prod:

(seems to be doing this on all of the vue-selects)

https://cla-groups-dev.oit.umn.edu/reports/lastModified

dev:

Prod:

Steps to reproduce:

1. edit a group
2. remove a member (not the last one in the list)

-> result: all of the "role" boxes below the person you removed go blank.

• add start semester / end semester dropdowns, ideally going back 5 years as an option
• remove section number
• add enrollment info in parens (35/100) after course. May eventually make that a hover state or something.
• Add filter by course level - grad/undergrad. Undergrad are courses <5000, grad are >=5000
• Add filtering by appointment type - faculty, teaching specialist, etc. This will be filtering on jobcode by employee, which I definitely need to add to the API
• start visible part of the table centered on current semester (if not too complex)

https://cla-groups-dev.oit.umn.edu/role/21

Doesn't seem to display any results, even though the api call is returning one?

DeV:

Prod:

use one of the Excel packages to generate an XLS file with a tab for each of our views

dev:

prod:

Let users "pivot" the scheduling report view so that the courses are on the left and instructors who have taught the courses are listed in the cell.

Instructor data should still include leaves. Maybe an icon to indicate the instructor has a leave in a given term, and then users can expand the instructor item to see more details?

As a department admin, I need to know which of my faculty may be impacted by a leave in the upcoming spring semester.

A set of filters in the scheduling report, or a separate report, should give me a quick summary of only the folks impacted by a leave (eligible, confirmed, pending, etc) for a given term or timespan.

Sentry Issue: GROUPS-TOOL-24

ArgumentCountError: Too few arguments to function App\Library\UserService::__construct(), 0 passed in /swadm/var/www/html/releases/240/app/Console/Commands/ImportLeaves.php on line 33 and exactly 1 expected
  File "/app/Library/UserService.php", line 13, in App\Library\UserService::__construct
    public function __construct(Bandaid $bandaid) {
  File "/app/Console/Commands/ImportLeaves.php", line 33, in App\Console\Commands\ImportLeaves::handle
    $this->userService = new \App\Library\UserService();
  File "/artisan", line 37
    new Symfony\Component\Console\Output\ConsoleOutput
...
(11 additional frame(s) were not displayed)

• should we be able to search across groups / roles / users?
• Search retired groups