Remix

Make your own version of Campus Issue Tracker

Edit the prompt below and generate a customized version in seconds.

Original by dsamy3877

Describe your app

Create a complete Cloud-Based Campus Problem Reporting and Management System as a final-year/student academic project.

Project Objective

Develop a web-based cloud application that allows students and staff to report campus problems such as classroom issues, electrical problems, water problems, cleanliness, Wi-Fi/network issues, laboratory equipment problems, hostel issues, and other campus-related complaints. Administrators and maintenance staff should be able to view, assign, update, track, and resolve complaints.

User Roles

1. Student/Staff
   
   - Register and login
   - Submit a complaint
   - Select complaint category
   - Enter title and detailed description
   - Upload an optional image
   - Select location/block/department
   - View complaint status
   - Track complaint history
   - Give feedback after resolution

2. Admin
   
   - Secure login
   - Dashboard with total, pending, assigned, in-progress, and resolved complaints
   - View all complaints
   - Filter complaints by category, location, priority, and status
   - Assign complaints to maintenance staff
   - Change complaint priority
   - Monitor resolution time
   - Manage users and categories
   - View reports and statistics

3. Maintenance Staff
   
   - Login
   - View assigned complaints
   - Update status
   - Add work/update remarks
   - Mark complaint as resolved
   - View complaint history

Complaint Status

Use:

- Submitted
- Pending
- Assigned
- In Progress
- Resolved
- Reopened
- Closed

Important Features

- Authentication and role-based access
- Complaint submission
- Complaint ID automatically generated
- Image/file upload
- Complaint tracking
- Priority levels: Low, Medium, High, Critical
- Automatic timestamp
- Assignment to maintenance staff
- Status update history
- Notifications
- Search and filtering
- Admin dashboard
- Analytics using charts
- Feedback/rating after resolution
- Complaint reopening option
- Responsive UI for mobile and desktop

Cloud Architecture

Design the project using cloud architecture:

User → Frontend → Backend/API → Cloud Database → Cloud Storage

Explain how cloud services are used for:

- Application hosting
- Database storage
- Image/file storage
- Authentication
- Scalability
- Backup and security

Suggested Technology Stack

Frontend:

- React.js
- HTML
- CSS
- JavaScript
- Bootstrap or Tailwind CSS

Backend:

- Node.js
- Express.js

Database:

- MongoDB Atlas / Cloud Database

Cloud:

- Firebase or another suitable cloud platform for authentication/storage
- Deploy frontend and backend using suitable cloud hosting platforms

Database Collections/Tables

Create suitable schemas for:

- Users
- Complaints
- Categories
- Assignments
- StatusHistory
- Feedback
- Notifications

Dashboard

Create separate dashboards for Admin, Student/Staff, and Maintenance Staff.

Admin dashboard should display:

- Total Complaints
- Pending Complaints
- In Progress
- Resolved
- Critical Issues
- Category-wise complaints
- Location-wise complaints
- Monthly complaint statistics

UI Pages

Create:

1. Landing Page
2. Login
3. Registration
4. Student/Staff Dashboard
5. Submit Complaint
6. My Complaints
7. Complaint Details & Tracking
8. Admin Dashboard
9. All Complaints
10. Assign Complaint
11. Maintenance Dashboard
12. Assigned Complaints
13. Profile
14. Notifications
15. Feedback Page

Extra Innovation

Add an Emergency/Critical Issue Reporting feature where critical campus problems are highlighted immediately for administrators.

Add a duplicate complaint detection feature if possible, so similar complaints from the same location can be identified.

Development Requirements

Provide:

1. Complete project architecture
2. Folder structure
3. Database schema
4. API design
5. Frontend code
6. Backend code
7. Authentication implementation
8. CRUD operations
9. Cloud database connection
10. File/image upload implementation
11. Role-based authorization
12. Dashboard implementation
13. Deployment steps
14. Testing procedure
15. Sample data
16. README documentation

The project should be clean, modern, responsive, beginner-friendly, modular, and actually runnable.

Do not provide only a prototype or static UI. Build the complete working application with frontend, backend, database, authentication, cloud integration, APIs, and deployment instructions.

Also explain the complete request → API → database → response flow and provide a simple architecture diagram suitable for project presentation.

Free to use. No credit card required.