Ticketit Legacy Laravel Package

Product Decisions This Supports

• Internal Tooling: Build a lightweight, self-hosted helpdesk/ticketing system for internal teams (e.g., support, IT, or customer-facing ops) without relying on third-party SaaS solutions.
• Legacy System Replacement: Migrate from outdated ticketing systems (e.g., custom PHP, outdated Laravel versions) to a modern, maintainable Laravel-based solution.
• Cost Efficiency: Avoid licensing fees for enterprise ticketing tools (e.g., Zendesk, Freshdesk) for small-to-medium teams with simple needs.
• Custom Workflows: Tailor ticketing logic (e.g., custom fields, statuses, or automation) without vendor lock-in.
• Data Control: Host tickets on-premises or in a private cloud to comply with strict data residency/privacy regulations (e.g., healthcare, finance).
• Roadmap Flexibility: Use as a starting point to extend functionality (e.g., add APIs, integrations, or analytics) as needs evolve.

When to Consider This Package

• Avoid if:
  • You need active maintenance (package is unmaintained; last commit in 2019).
  • Your team requires scalability (e.g., >10K concurrent users or high-volume attachments).
  • You need modern Laravel features (Laravel 7+ compatibility is untested; assumes legacy auth).
  • Enterprise-grade features are critical (e.g., SLA tracking, multi-channel routing, or advanced reporting).
  • You lack PHP/Laravel expertise to customize or debug the package.
• Consider if:
  • You’re on Laravel 5.1–6.x and need a quick, no-frills ticketing system.
  • Your use case is simple (e.g., internal IT tickets, basic customer support).
  • You’re willing to fork/maintain the package for long-term use.
  • Budget or compliance prevents SaaS adoption.

How to Pitch It (Stakeholders)

For Executives: "This package lets us build a lightweight, self-hosted ticketing system for [X team] without recurring SaaS costs. It integrates with our existing Laravel auth, so no new user management is needed. While it’s not feature-rich like Zendesk, it’s a cost-effective way to replace our outdated [legacy tool] or avoid vendor lock-in. We’d need to allocate time for customization and maintenance, but the upfront savings and data control justify the trade-off."

For Engineering: *"This is a minimal Laravel ticketing system for L5.1–6.x that we could deploy in a few weeks. Key pros:

• Pros: MIT license, simple setup, tight Laravel auth integration.
• Cons: Unmaintained (last commit 2019), no Laravel 7+ support, limited features. Recommendation: Use as a starting point if we can accept the risks. We’d need to:

1. Test compatibility with our Laravel version.
2. Plan for forking/maintenance (e.g., security patches, bug fixes).
3. Extend functionality (e.g., add APIs, notifications) to meet our needs. Alternative: Build from scratch if the package’s limitations are dealbreakers."*