Add ability for people to filter tickets that they see

Admin should be able to filter what tickets they see (open, claimed, closed, canceled)
Mentors should also be able to filter tickets they see (open, claimed, tickets they claimed (?))

In addition, the ticket queue should be automatically sorted such that the most recent tickets are on top, older tickets on bottom. For users, their closed tickets should be shifted to the bottom. For Mentors, their Claimed tickets should be on top.

How you filter is up to you. Maybe have a bunch of checkboxes for each type of status and show those that are checked off?

• Notification button (for ex: bell icon) on menu to allow sound notifications to be enabled/disabled
• Component to allow for sound alerts
• If sound alert is enabled, play notification when: 1) Mentor: New ticket is added to ticket queue 2) User: Ticket has been claimed

Create an admin page for Director users that will allow them to

• View list of mentors with average rating [MENTORS]
• View all closed tickets and associated rating/feedback [TICKETS]
• Stats -> number of mentors, number of unique users for MentorQ, number of tickets, average claimed/closed time [STATS]

• only mentors can see
• list current open ticket
• claim a ticket
• show the location of a ticket
• close / reopen a ticket (does not delete)

Have how long a ticket has been open displayed on open tickets. Should say xx minutes until it hits an hour. After that it should say xx hours.

• Add preview picture (HackRU logo)
• Change title from React App to MentorQ
  Resources

Edit the way the claim/closed system works for the tickets.

State: OPEN -> can be CLAIMED by Mentor/Admin
State: CLAIMED -> can be OPENED or CLOSED by Mentor/Admin
State: CLOSED -> can be REOPENED by Admin

Make sure to only display buttons related to the possible options for that particular ticket status

Potentially move the useStyles hooks into a separate file if it's more than like 20 lines long (RE: ticket.index.js). Double check to see if this is possible.

When a ticket is claimed, send a notification to both the mentor claiming, and the hacker who sent the ticket with a slack DM link

• User notified when their Ticket is Claimed/Closed/Reopened
• Associate user with Slack-ID, User should be able to know if they have a Slack-ID set or not
• Modify NewTicket Panel UI to default to slack-ID instead of Contact if Slack-ID set (Dropdown to switch to contact?)
• Mentor should be forced to have Slack-ID, otherwise cannot claim/close tickets (prompt to frontend?)
• Upon Claiming Ticket, Mentor is given slack dm link (Should it also show up in user notification of claimed ticket?) -> feed ticket to backend and receive link

Write tests with Jest to check if all the pages and components render properly

show the mentor who claimed a hackers ticket, (eventually also show the dm link)

Add a new field on tickets from backend called "active" which can either be true or false, and true by default

Most of this is already there, but essentially when a mentor or user scrolls, only the tickets should scroll while the navbar and ticket-submission-panel stays in place (the ticketpanel already does this, but the nav bar doesn't)

YAY this one has a license file, but its not MIT lmfao

• Specify contact information to be cell phone number, email etc.
• Update design - See design mockup for sample

Check how many requests are being made for the leaderboard and feedback pages for the admin page. We need to reduce how often these requests are being made.

Whenever someone opens a ticket, their name should be on that ticket so we know who we're talking to. In addition, on top of the ticket panel, add a "Hi there NAME \n How many we help you?"

• Name of user who Opened Ticket is on Ticket
• Send user's name when they post a ticket
• Anonymous Checkbox option to send Anonymous name instead
• Display Hi there "NAME"

Create a Mock for MentorQ for the Material-UI redesign.

perhaps detect when a ticket's comment is long and have it in its own row with other data in a second row at the bottom. this avoids the comment squishing all the other content on the ticket card

queue status is essentially an object {open:true|false,mentorsOnDuty:number}
the mock api needs

• a way to set queue status
• a way to attach a handler to get updates when the status has been updated

• Add an icon showing whether a ticket is active (two states: active, inactive)
• All closed/cancelled tickets are inactive
• Users/Mentors/Directors can change whether or not a ticket is active/inactive

• Make it look cooler when we have an invalid login (also edit logic so loading state is not entered unless request is valid)
• Hide Password field (Or at least toggle visibility)
• Find a way to fix the Inputs for the login page (make white, enter should submit)
• Add a header that says Sign In

Find a way to escape infinite loading when it arises (timeout)
Find a way to force logout when a user is logged in and LCS fails

Find suitable way to deploy MentorQ frontend

Reduce Volume of Requests by only pulling most updated feedback on login and when edit feedback button is clicked. In addition, change ticket update interval from 3 seconds to 30 seconds

Admin should be able to delete tickets

• Post to backend to update ticket status to "Deleted"
• Reflect change in the frontend (filter out "Deleted" tickets)

User should be able to cancel an open ticket (essentially like deleting a ticket)

** Things to consider **

• Option to explain why ticket was deleted?
• Mention something in frontend about the fact we're not truly deleting tickets

We want to reduce the amount a mentor/director needs to scroll to look at tickets especially if we have a ton of them open

• Cap number of Open/Claimed Tickets a user can have at a time to 5

Modify certain components (Especially typography) to scale to Mobile.
Consider creating a separate navbar for mobile and separate out newticket form from the ticket list.
Think about how we want to represent the admin page for Mobile (More options in the navbar?)

Ability to mark mentors on/off duty and display the number of mentors who are active to hackers. (if 0, then queue is closed, otherwise is open)

Show mentor feedback button on the non-expanded view of user's closed ticket (for ex: separate small feedback icon on top right corner of ticket)

• Turn button and other small items into separate components to reduce code clutter
• Other code cleanup and remove redundancies

Modify it such that only the Mentor who claimed a ticket can close it (a Mentor shouldn't be able to close another mentor's ticket)

Load a newly posted ticket from the user so they don't have to wait 30 seconds for it to update

• If time open is less than 1 hour, give time open in minutes
• Only show time open for tickets with status "OPEN"

Read in User/Mentor name and role data from JWT token passed in from backend.

• show all tickets open and closed
• show response/close times
• other stats (todo)

react router might help us organize the views.

Upon claiming ticket, Hacker, mentor, admin should be able to

• See which mentor had claimed the ticket

Upon closing tickets, Hacker should be able to

• Rate the experience with this specific mentor (out of 5 stars)
• Give a short blurb about their experience

Admin Page

• Should be able to view the average of ratings for each mentor that has closed a ticket
• View feedback associated with all claimed tickets
• Be able to open closed tickets

• Uniform styles for each ticket (already sorted into active/closed) - font, font color, ticket color etc.
• Add styling - See design mockup for sample

add a button in mentorq that could update their status
would require a new feature to be added to the api

Give an error when the user inputs a comment that is longer than 255 characters while creating a ticket (cannot submit tickets with comments longer than 255 characters)

force slack usage with mentorq.

• if a user doesn't have a slack account linked, they cannot fill out the ticket
• perhaps disable/gray out the submit button and show another button that says "link your slack account to create tickets" that sends you to the frontend page for linking slack accounts
• if a user has a slack account linked, then this will be used for mentors to dm mentees on slack

Make the fields more modular, so removing/adding fields is as simple as saying enabled/disabled before every semester rather than having to modify tons of code and then re-adding it

Update Readme, add what our mission, history, how to set up etc...

Make the "Help Me!" button disabled until all fields have values in them

Research Material-UI and work with frontend to make MentorQ design consistent with HackRU website. Frontend should only need to send us a theming file every semester to update our theme.

• Login Page (Kayla)
• Hacker/Admin/User Pages (Serena)

• open close queue
• set amount of mentors on duty

• Create a feedback form with /5 rating and feedback box for hacker when a ticket is closed

• Fetch feedback endpoint to display data on all closed tickets (feedback, rating)

• Display ranking of mentors (admin only or everyone?)

make a new page login/splash page. it should:

• take in callback to handle login event
• have a loading pinwheel type thing

• tell hacker if the queue is closed
• show amount of mentors on duty
• form for hacker to open ticket
• tell hackers when their ticket is claimed and name the mentor on the way
• add back map pinning