Revamp the Support Ticket Index page

[garettarrowood]

Summary

Our current Support Ticket page represents the first pass at this view. It needs new/changed columns, sortability, and revamped styling.

Criteria for Completion

• [ ] Headers on page match the header names in the mockup (in the right order)
• [ ] Correct data shows up for each column
• [ ] Standard sorting (follow conventions of Volunteers page) are added to the "Requested By", "Date Created", "Student" (sort on last name), "Staff Contact" (sort on last name), and "Type" . If some sorting seems too hard to get done in this deliverable, it can be moved into another issue.
• [ ] Nav item STAYS "Tickets", but page title is updated to "Support Tickets"
• [ ] (No need to implement any filtering yet. That feature will come in another issue.)

What does each column represent?

• "Requested By:" is what is currently showing up as the "Requestor"
• "Date Created" is what is currently showing up as "Created At"
• "Response ID" is the survey_response_id on the support_ticket. These only exist on "Support" Type tickets. There is no need to make this a link yet, just the ID is fine.
• "Student" is the student associated with the related survey_response. These only exist on "Support" Type tickets as well. If there is no survey_response on the ticket, this field will be left blank.
• "Staff Contact" is the name of the active staff contact associated with the student (for "Support" type tickets). If the requestor IS an admin, the staff contact shows the admin name again (admin == staff). If it's a "Contact" type, drop in the name(s) of the volunteer's students' active staff contact. This will likely only be one name, but could be more that one.
• "Type" is the support ticket category. survey_response => "Support". admin => "Admin", contact_info => "Contact".
• "Action" is the status, but also the link to the resolve form. So where there is a "View" link now, it may become a "Resolve" link that goes to the same place. Or a "Closed" link that also goes to the same place.

How it looks now:

How it will look after this update

(Disregard the filter input - and disregard the different table style.) Also, we will not be adding an import button to this view.

[goromlagche]

Hello @garettarrowood , I would like to work on this.

disregard the different table style

By this, do you mean the change in CSS in the new screenshot?

[garettarrowood]

@goromlagche - Essentially, yes.

This style:

Does not yet need to change to this style:

Because when we do so, it would be good to update the style of all 4-5 tables at once instead of making one look different than the rest.