I recently started working at a company without a formal ticketing system, and the lack of incident control is causing issues for IT management and reporting. With no budget for commercial solutions, I urgently need suggestions for setting up a basic, functional help desk system. Specifically, I'm looking for:
1. **Free/Open-Source Solutions:** Something I can install on a spare local server.
2. **Serverless/Low-Cost Options:** Creative solutions using tools like Google Forms/Sheets or Microsoft Lists/Flow that can act as a ticketing system (automated email notifications for new tickets would be great!).
The key requirements include:
- Ability for users to submit tickets (incident logging).
- Simple status tracking (Open, In Progress, Closed).
- Bonus if it allows for ticket assignment, even manually.
Has anyone found a reliable zero-cost solution for managing incidents? What tools or methods have you successfully used?
6 Answers
For smaller teams, Jira Service Desk offers a free tier with a few seats. Might be worth looking into, but it gets complicated with larger teams.
You can find GLPI [right here](https://www.glpi-project.org/en/downloads/). I'm unsure if it's still free, but I think it should serve your needs well!
I recommend looking into osTicket. It meets all your criteria for a ticketing system and has been reliable for many users. It's user-friendly too!
1) You might want to dig through the past discussions and resources shared; this topic comes up often. 2) Just a heads-up, no solution is truly zero-cost. Setting it up can take considerable time and effort to customize for your needs. 3) We've been using znuny, which has a quirky name but works well enough right out of the box. Look into other free options first; there might be ones that suit you better!
GLPI is a free and open-source tool that covers help desk needs and asset management. It's a solid solution—definitely worth checking out!
Absolutely! GLPI has been a game-changer for us compared to using a simple Microsoft list. It's great having the option to mark solutions as a knowledge base for future reference.
I'm a bit perplexed about the term 'self-hosted' vs. 'serverless.' Aren't those kind of contradictory?
It's an inside joke! Some people refer to serverless systems as those running on Docker because, you know, Docker's not really on traditional servers—it's on whatever they can run it on!
Another plus for osTicket! I used it for years before making a switch, and it works great.