-
Notifications
You must be signed in to change notification settings - Fork 2
Home
GoobyDesk is a simple, lightweight, databaseless service desk for Home Labbers, Families, and very Small Businesses.
It features a homepage, a login page, and a dashboard. On the homepage (index.html) external users can submit a ticket. When a user submits a ticket, it's content is written to the local tickets.json file.
Once the ticket has been written, an email containing the ticket-id and original ticket are sent to the end user provided email. The email is sent from the email box defined in the .env file.
There is a background thread defined in the code that monitors the inbox for incoming replies. If a reply is detected, it is scraped and put into the notes variable in the tickets.json file. This occurs every five minutes via graceful login and logout process.
The dashboard displays Open or In-Progress tickets.
Use as few dependencies as possible. When multiple package options are available; use the one with the best documentation.
Update CHANGELOG when pushing code/function changes.
When making code changes, ensure the following features work as designed....
- User tickets generate email threads.
- Technician can login to the dashboard.
- Email replies append to the notes of the tickets.json file.
- Closed tickets are hidden from the Dashboard but remain in the tickets.json file.
- Technician can successfully logout.
- All 4x HTML pages look "correct".
- Index, Login, Dashboard, Ticket Commander
- Protected pages cannot be loaded without the session cookie
- Console is not logging HTTP errors
No expectations are defined yet.
- HTML Form does not perform GOOD input validation
- Replies appending to notes can get long-winded as the thread gets larger.
- The employee login cannot contain certain but unknown characters. "-" seems to cause issues.
- The code can be fragile to changes
- There is no visible error message when technician login fails
- There is no visible confirmation when a ticket has been submitted.