Skip to content
TheChatArchiveThe Chat Archive
grok-3-mini-beta· xAIHugging Face LMArena Human Preference 140K

Free & Open source ticketing systems, which is lightweight and can turn an email message…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Claudeclaude-3-5-haiku-20241022’s answer.
  1. User

    Free & Open source ticketing systems, which is lightweight and can turn an email message into a work item, and track its progress. list popular open-source ticketing systems with this capability.

  2. Assistant

    Below is a response to your query about free and open-source ticketing systems. I'll focus on those that are generally considered lightweight (i.e., easy to install, low resource requirements, and simple to use), and specifically highlight systems that can automatically convert an email message into a work item (e.g., via email integration or piping) and track its progress. These systems are popular in the open-source community and are actively maintained as of my last update.

    Key Criteria for Selection:

    • Free and Open Source: All listed systems are licensed under open-source licenses (e.g., GPL, AGPL) and are freely available.
    • Lightweight: They have minimal system requirements, straightforward setups, and don't require extensive hardware or complex configurations.
    • Email to Work Item: The system must support incoming emails to automatically create tickets (work items) and allow tracking of their status (e.g., open, in progress, resolved).
    • Popularity: Based on community adoption, GitHub stars, and usage in real-world scenarios.

    Popular Open-Source Ticketing Systems

    Here's a list of the most relevant options. I've included a brief overview, key features, and why they fit your criteria. You can check their official websites for installation guides and documentation.

    1. Zammad

      • Description: Zammad is a modern, user-friendly ticketing system derived from OTRS. It's designed for customer service and IT support, making it ideal for converting emails into tickets.
      • Key Features:
        • Automatically turns incoming emails into tickets via its built-in email channel.
        • Tracks ticket progress with customizable workflows, SLAs, and status updates (e.g., new, in progress, closed).
        • Lightweight: Requires minimal resources (e.g., runs on a standard LAMP stack) and has a simple web-based interface.
        • Additional perks: Integrates with tools like Slack, LDAP, and calendars; supports multi-channel inputs (email, chat, etc.).
      • Why it fits: It's free (AGPL-licensed), actively maintained, and popular among small to medium teams.
      • Resources: Website - zammad.org; GitHub stars: ~4,000.
      • Potential Drawbacks: May require some configuration for advanced email setups.
    2. OSTicket

      • Description: OSTicket is a simple, web-based ticketing system focused on helpdesk and support operations. It's lightweight and excels in email-driven workflows.
      • Key Features:
        • Converts emails into tickets using email piping or IMAP/POP3 integration.
        • Tracks progress with ticket assignments, priorities, and status updates (e.g., pending, resolved).
        • Lightweight: Easy to install on shared hosting or a basic server; doesn't need high-end hardware.
        • Additional perks: Supports knowledge bases, user portals, and plugins for extensions.
      • Why it fits: It's free (GPL-licensed), straightforward for beginners, and widely used in small businesses and non-profits.
      • Resources: Website - osticket.com; GitHub stars: ~2,500.
      • Potential Drawbacks: The community edition is basic; paid add-ons exist for advanced features.
    3. Request Tracker (RT)

      • Description: RT is a flexible ticketing system originally developed by Best Practical, used for IT support, project management, and email-based workflows.
      • Key Features:
        • Automatically creates tickets from emails via its powerful email gateway.
        • Tracks progress with queues, custom fields, and workflows (e.g., track from "open" to "stalled" to "resolved").
        • Lightweight: Runs on modest servers and has a simple command-line or web interface; it's highly customizable without being bloated.
        • Additional perks: Supports integrations with email servers, Active Directory, and other tools; great for automation scripts.
      • Why it fits: It's free (GPL-licensed), battle-tested in large organizations, and popular for its reliability in email handling.
      • Resources: Website - bestpractical.com/rt; GitHub stars: ~1,500 (as it's more mature).
      • Potential Drawbacks: The interface can feel dated compared to newer systems, but it's still efficient.
    4. OTRS (Open Ticket Request System)

      • Description: OTRS is one of the oldest open-source ticketing systems, focused on IT service management. It's the predecessor to Zammad and remains popular for its email capabilities.
      • Key Features:
        • Turns emails into tickets using its email-to-ticket feature, with support for multiple mailboxes.
        • Tracks progress via detailed ticket histories, SLAs, and escalation rules (e.g., monitor from "new" to "in progress").
        • Lightweight: Installs quickly on a standard web server and is designed for low-resource environments.
        • Additional perks: Includes process automation, reporting, and integrations with CMDBs or other systems.
      • Why it fits: It's free (AGPL-licensed), widely adopted in enterprises, and excels in email-based ticketing.
      • Resources: Website - otrs.com; GitHub stars: ~1,000 (with community forks).
      • Potential Drawbacks: Some users find it less intuitive than Zammad; it's more feature-rich, which might make it feel less "lightweight" for very small setups.

    Additional Recommendations:

    • Why these are popular: These systems are among the most downloaded and starred on platforms like GitHub. They balance functionality with simplicity, making them suitable for small teams, startups, or personal use.
    • Installation Tips: Most of these can be installed on a Linux server with tools like Apache, MySQL, and PHP (LAMP stack). For email integration, you'll need to configure your email server (e.g., via IMAP or SMTP) and set up piping rules.
    • Alternatives to Consider: If you need something even more minimal, look into Flyspray (more for bug tracking) or MantisBT, but they may not be as robust for email-to-ticket workflows. GLPI is another option, but it's more comprehensive (and less lightweight) due to its asset management focus.
    • Community and Support: All these projects have active communities on forums, GitHub, and their official sites. Check for the latest versions to ensure compatibility and security.

    If you have specific requirements (e.g., preferred operating system, scalability needs, or integrations), I can refine this list further!

  3. User

    Include their programming language for each, and the platform / frameworks that each depends upon.

  4. Assistant

    Below is an updated version of my previous response to your query about free and open-source ticketing systems. I've expanded each entry to include:

    • Programming Language: The primary language used to develop the system.
    • Dependent Platforms/Frameworks: A summary of the key platforms (e.g., operating systems), frameworks, databases, and other dependencies required for installation and operation. This is based on the systems' documentation and typical setups.

    I've kept the overall structure the same for clarity, integrating these details into a new subsection under each system. This will help you understand the technical requirements if you're planning to deploy any of these.

    Popular Open-Source Ticketing Systems

    Here's the list with the added technical information.

    1. Zammad

      • Description: Zammad is a modern, user-friendly ticketing system derived from OTRS. It's designed for customer service and IT support, making it ideal for converting emails into tickets.
      • Key Features:
        • Automatically turns incoming emails into tickets via its built-in email channel.
        • Tracks ticket progress with customizable workflows, SLAs, and status updates (e.g., new, in progress, closed).
        • Lightweight: Requires minimal resources (e.g., runs on a standard LAMP stack) and has a simple web-based interface.
        • Additional perks: Integrates with tools like Slack, LDAP, and calendars; supports multi-channel inputs (email, chat, etc.).
      • Technical Details:
        • Programming Language: Ruby.
        • Dependent Platforms/Frameworks: Built on the Ruby on Rails framework; requires a Linux-based operating system (e.g., Ubuntu, CentOS); databases like PostgreSQL or MySQL; web servers such as Nginx or Apache; and Ruby version managers like RVM or rbenv for dependency management.
      • Why it fits: It's free (AGPL-licensed), actively maintained, and popular among small to medium teams.
      • Resources: Website - zammad.org; GitHub stars: ~4,000.
      • Potential Drawbacks: May require some configuration for advanced email setups.
    2. OSTicket

      • Description: OSTicket is a simple, web-based ticketing system focused on helpdesk and support operations. It's lightweight and excels in email-driven workflows.
      • Key Features:
        • Converts emails into tickets using email piping or IMAP/POP3 integration.
        • Tracks progress with ticket assignments, priorities, and status updates (e.g., pending, resolved).
        • Lightweight: Easy to install on shared hosting or a basic server; doesn't need high-end hardware.
        • Additional perks: Supports knowledge bases, user portals, and plugins for extensions.
      • Technical Details:
        • Programming Language: PHP.
        • Dependent Platforms/Frameworks: Built with PHP; typically runs on a LAMP (Linux, Apache, MySQL, PHP) stack; requires a web server like Apache or Nginx; databases such as MySQL or MariaDB; and may use frameworks like Laravel for certain extensions (though the core is vanilla PHP).
      • Why it fits: It's free (GPL-licensed), straightforward for beginners, and widely used in small businesses and non-profits.
      • Resources: Website - osticket.com; GitHub stars: ~2,500.
      • Potential Drawbacks: The community edition is basic; paid add-ons exist for advanced features.
    3. Request Tracker (RT)

      • Description: RT is a flexible ticketing system originally developed by Best Practical, used for IT support, project management, and email-based workflows.
      • Key Features:
        • Automatically creates tickets from emails via its powerful email gateway.
        • Tracks progress with queues, custom fields, and workflows (e.g., track from "open" to "stalled" to "resolved").
        • Lightweight: Runs on modest servers and has a simple command-line or web interface; it's highly customizable without being bloated.
        • Additional perks: Supports integrations with email servers, Active Directory, and other tools; great for automation scripts.
      • Technical Details:
        • Programming Language: Perl.
        • Dependent Platforms/Frameworks: Written in Perl; requires a Unix-like operating system (e.g., Linux or FreeBSD); databases like PostgreSQL, MySQL, or Oracle; web servers such as Apache with mod_perl; and templating frameworks like Mason for its user interface.
      • Why it fits: It's free (GPL-licensed), battle-tested in large organizations, and popular for its reliability in email handling.
      • Resources: Website - bestpractical.com/rt; GitHub stars: ~1,500 (as it's more mature).
      • Potential Drawbacks: The interface can feel dated compared to newer systems, but it's still efficient.
    4. OTRS (Open Ticket Request System)

      • Description: OTRS is one of the oldest open-source ticketing systems, focused on IT service management. It's the predecessor to Zammad and remains popular for its email capabilities.
      • Key Features:
        • Turns emails into tickets using its email-to-ticket feature, with support for multiple mailboxes.
        • Tracks progress via detailed ticket histories, SLAs, and escalation rules (e.g., monitor from "new" to "in progress").
        • Lightweight: Installs quickly on a standard web server and is designed for low-resource environments.
        • Additional perks: Includes process automation, reporting, and integrations with CMDBs or other systems.
      • Technical Details:
        • Programming Language: Perl.
        • Dependent Platforms/Frameworks: Written in Perl; requires a Linux-based operating system (e.g., Debian, Red Hat); databases like MySQL, PostgreSQL, or Oracle; web servers such as Apache with mod_perl; and may use Perl frameworks like CGI or Template Toolkit for its web components.
      • Why it fits: It's free (AGPL-licensed), widely adopted in enterprises, and excels in email-based ticketing.
      • Resources: Website - otrs.com; GitHub stars: ~1,000 (with community forks).
      • Potential Drawbacks: Some users find it less intuitive than Zammad; it's more feature-rich, which might make it feel less "lightweight" for very small setups.

    Additional Recommendations:

    • Why these details matter: Knowing the programming language and dependencies can help you assess compatibility with your existing infrastructure. For instance, if you're on a Windows server, systems like Zammad or OSTicket might require additional setup (e.g., using WAMP for OSTicket), while Perl-based ones like RT and OTRS are more native to Linux environments.
    • Installation Tips: Most of these systems are designed for Linux servers. Use package managers like apt or yum for dependencies. For email integration, ensure your email server (e.g., Postfix or Sendmail) is configured properly.
    • Alternatives to Consider: If you're looking for something in a different language, tools like Flyspray (PHP-based) or MantisBT (PHP) could be explored, but they may not match the email-to-ticket capabilities as closely.
    • Community and Support: Check the official documentation for each system for detailed setup guides. Versions and dependencies can change, so verify with the latest releases on their GitHub repositories.

    If you need more specifics, such as step-by-step installation instructions or comparisons based on your environment, let me know!

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.