arpadgbondor / brad_traversy-react_front_to_back_2022-05-support_desk

Brad Traversy - React Front To Back 2022 - 05 - Support Desk

Udemy - Brad Traversy - React Front To Back 2022

• Section 17: MERN Project Start, API & Backend Authentication
• Section 18: Frontend Authentication
• Section 19: Tickets Functionality
• Section 20: Notes Functionality & Deploy

Description

The project is a full stack application, that allows users to register, login, create helpdesk tickets, close tickets, and communicate with customer service by making notes under the tickets. The customer service side login, and handling tickets is not included in the project.

I'm looking for contributors to develop the customer service side of the project

I opened an issue for discussion, if anyone would be interested in doing some team work, practising to do pull requests, contributing to someone else's repository, reviewing code in pull requests, etc... You can find the issue here.

Yes, I could do it myself, but I already have 150+ repositories I've built myself, and very little experience in working with others, so I tought I'd give it a try.

Deployed

• Deployed on Heroku

Used Tools:

• Frontend:
  • React.js
  • Redux toolkit
• Backend:
  • Express.js server
  • Authentication
  • MongoDB - Mongoose

Mayor changes:

• Bugfixes added from instructor's repository.

Environment variables:

• Create a file named .env and set these variables:
  • NODE_ENV - development
  • PORT - server's port number
  • MONGO_DB_CONNECT - Moingo DB connection string
  • JWT_SECRET - JSON Web Token Secret string

Resources:

• The source code of the instructor's solution is in this Github repo

brad_traversy-react_front_to_back_2022-05-support_desk's Issues

Feature needed: Backend - View any single ticket as a staff member

Backend GET /api/tickets/:ticketID endpoint should return any ticket regardless of the owner if the user is staff member.

Originally posted by @ArpadGBondor in #1 (comment)

The customer service side login and handling tickets is not included in the project.

I opened an issue for discussion, if anyone would be interested in doing some team work, practising to do pull requests, contributing to someone else's repository, reviewing code in pull requests, etc...

Yes, I could do it myself, but I already have 150+ repositories I've built myself, and very little experience in working with others, so I tought I'd give it a try.

Feature needed: Backend - Staff members should be able to comment on any ticket

Backend POST /api/tickets/:ticketID/notes/ endpoint should allow creating new tickets if the user is staff member.

Originally posted by @ArpadGBondor in #1 (comment)

Feature needed: Backend - Query for every open ticket and every new ticket

Backend GET /api/tickets endpoint should take a query parameter, and if the user is staff member, the endpoint should be able to return either every open or every new ticket in the database.

Originally posted by @ArpadGBondor in #1 (comment)

Add bugfixes from the bugfix branch of the instructor's repository

Hi guys, yeah this is a good idea. I'm happy to add what I can.
You may be interested in checking out the bugfix branch of Brad's repository where I've been tracking and fixing many of the bugs found by students in the course, some from you @ArpadGBondor !
It's also been streamlined and simplified a good deal in terms of state management as there is no real need for a isLoading, isSuccess or reset state functions in tickets and notes. In most cases we can infer loading from presence or absence of data and leverage pending, fulfilled and rejected states provided by our AsyncThunkAction to reset state.
Also the useAuthStatus hook was removed as it was only really a wrapper for Redux state and only used in one place - PrivateRoute.jsx.
PrivateRoute also got refactored to no longer use an <Outlet /> as we were not really doing any nested routing so a <Outlet /> was not necessary.
I haven't documented all the changes as yet but there are notes in the code where it has been changed and why.
I think the code from the bugfix branch would be a more stable and predictable base to start from for adding in additional features.
I'd be happy to submit a PR with the bug fixes if you like?

Originally posted by @bushblade in #1 (comment)

Feature needed: Frontend - Show if the user logged in is a staff member

After logging in, we should always be able to tell if we are looged in as a staff member, or as a customer. (maybe by having different background color)

Originally posted by @ArpadGBondor in #1 (comment)

Feature needed: Email verification after registration

To prevent anyone signing up for a staff account I would also suggest adding in email verification so that the app sends an email (nodemailer or mailgun) to the email address with a link to click and confirm email.
This would also mean you need to add in some properties to the User model like a pending and active state for each member. This would start as pending and then once they have verified the email they are changed to active and can sign in.
For the link you can generate some kind of uuid or JWT and save that in their model/document in the DB, then they click the link in the email which takes them to the app at some end point like /confirm/:comfirm_token so using req.params in express to get the confirm_token. Then query the user by the confirm token, change their pending status to active and send back a jwt or a message for them to login.

Originally posted by @bushblade in #1 (comment)

Feature needed: Register as a staff member

Add a new environment variable to store the staff e-mails domain name.
If during registration the email address has the same domain name, register it as a staff member. (or ask if the user wants to register customer or staff member.)

UserModel already have an isAdmin property to show if the user is staff member.

Originally posted by @bushblade in #1 (comment)

Feature needed: Frontend - Create TicketList component

Extract TicketList component from Tickets page that can be used to display different query results on different pages

Originally posted by @ArpadGBondor in #1 (comment)