A Jira-like ticket tracker built with MERN stack by 3 fullstack web dev students: Michael Fernandez, Jenny Webster & Enzo Morales.
This project aims to create a basic ticket tracker application similar to JIRA. It is the final assessment for our Web Development course and serves as an evaluation of our ability to create a fullstack MERN application.
- MERN (MongoDB, Express, React, Node)
- Additional libraries: CORS, bcryptJS, JsonWebToken, Bootstrap, Nodemon, React-Router, uuidv4
- User registration and login
- Ticket creation, editing, and deletion
- Displaying a list of user's tickets
- Enhanced user authentication (password encryption, ID Tokens, logout functionality)
- Improved ticket management (advanced fields, sorting, filtering, pagination, quick edit modal)
- Project README
- Organization support (admin privileges)
- File attachments, user comments, and user tagging on tickets
- Integration with third-party APIs
We will focus on implementing the core features first, followed by the stretch goals, and finally the extended stretch goals if time permits.
To run the project locally, follow these steps:
- Clone the repository.
- Install dependencies:
npm install - Run the server:
npm start - Open your browser and navigate to
http://localhost:3000
We appreciate any feedback and contributions. Please feel free to submit issues or pull requests.
This project is licensed under the MIT License.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can't go back!
If you aren't satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you're on your own.
You don't have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify