ian-studios/computrack

ASP.NET Core Ticketing App designed to help my school manage it's issues and computers.

CompuTrack

Web-based ticketing program made with ASP.NET

Functionality:

This Web Application was designed for the EHS Help Desk/Hardware Software Maintenence Students as a means of tracking computers, assets, and issues with said assets. It kind of sucks, it was written in javascript. The end goal is to make a reliable way for students to access large quantities of data, without the nuisance of learning MS-Access as a Database manager.

Developers

Currently, Me (aka Aspectious) is the only one on this repo.

computrack's Issues

Security Flaws

Due to how "insecure" some of the requests can be, the server is secure, but the database is not necessarily secure. A lot of control is in the hands of the clients and is not the most secure platform, for now.

this is just a reminder for future me to increase security.

More documentation for future developers once I leave

Mental note: Learn to type the words "//" when making functions.

Assignment system so that helpdesk students can pick and choose their own issues to solve.

Custom Certificates?

Application needs a custom certificate to verify it's DNS Record.

New webpage organization

Site Planning (As of Now)

[ Dashboard ] [ Issue Center ] [ Explorer ] [ Inbox ] [ Help ]

• Dashboard - The main page, has links to all the other pages
• Issue Center - Page for Creating, Managing, and Discovering Issues
• Explorer - Explore all things data-related and find any type of object
• Inbox - Place where System Notifications as well as new comments on posts the user owns will show up
• Help - Help 4 dummies

It's not perfect but it gets the job done,

Advanced Filtering and Search System for Issue Center and Explorer

These systems allow for a more controlled and narrowed system for system administrators, students, and staff members to find what they are looking for in a nice, fast, and efficient way. ALSO MAKE IT USER-FRIENDLY, DO NOT FORGET TIHS.

Issue Properties Fetching and Editing System

System to fetch and edit the Properties of an Issue. Very important, needs to be done.

New Structuring of Issues into the "Issue Center" Rather than DB Explorer

Moving issue support from the explorer function to the "Issue Center" Function, allowing for a more flexible and user-friendly experience for teachers and students. Explorer will still be supported and still support advanced features with Issues.

Main Issue Center Views:

• My Issues (User Submitted issues or Issues assigned to a user)
• All Issues (List of All issues, useful for students to look for issues)
  • Supports Filters and Search (Advanced, Coming soon)
• New Issue (Self-Explanatory)

Account GUID Organization in DB1 Thanks to V4 UUIDs

Basically,
For each user that signs in, log their email address. We don't get their password, thankfully, but we store their email alongside a v4 UUID to identify users without their emails. This allows for easier and more organized data storage. It may also help us in the future if we choose to expand on this work already.

Handle new Database Editing with Issue editor

Kinda Important lol, depenednt on the new AJAX systems.

Updated to use AJAX for Endpoints.

Is fun.

Issue Creation System

While we move our systems to ASP.NET, we need a new system for a client to send a "New Issue Request" to the server. This method must be safe, secure, and functional.