Every (open source) software project needs a tool for bug reporting. Without such a tool it is hard because you need spreadsheets or mailing lists to manage todos. I think every developer knows why such tools are used

There are a lot of bug reporting tools like Bugzilla, JIRA, trac, Mantis, ... There are also a lot of project management tools with built-in ticket systems like Redmine.
It depends on your needs, if you develop open source or commercial software, the available money, ... which system is best suited.

We evaluated some systems and decided us for Flyspray.

Why?

We need a bug tracker that

• is also a change request management tool
• should be used from our customers (end-users)
• should not have tons of configuration options
• should be commercially useable
• should be open source
• should be easily adaptable
• should allow custom styles/themes
• should be template based
• should not waste development time

Many points have been met from different tools, but the popular tools were too complex or heavy weight. Flyspray is different, because it focuses on the basics. One of the problems are custom styles/themes. It supports custom themes but it does not support custom site templates.
But it offers most features that a professional system should have, it is small and easily adaptable - compared to other tools. And the tool is not only for developers. An end-user can handle it.

We knew that the system needs some tweaks. We added support for

• custom site templates (per project)
• custom mail templates (text, html, ..)
• enter officer for a ticket (group setting related), add effort (per ticket, per comment), add internal comments
• added a switch that disables global priorities/severities,status, ...
• set severity colors via database per project (instead of css)

This are some of our changes. We also fixed some layouting problems and created custom themes/templates.

If you are interested, look at our Flyspray installation:

SIB Visions Theme:
https://oss.sibvisions.com

Different style/site templates:
https://oss.sibvisions.com/index.php (WebUI)

If you are interested, leave a comment.

7 Responses to “Flyspray as Ticket/Support System”

1. saritha says:

   21/08/2012 at 13:31

   Plz send me more information about flyspray and its working and How to Install flyspray...
2. rjahn says:

   21/08/2012 at 16:36

   More information about Flyspray is available at http://www.flyspray.org.

   For installation, see http://www.flyspray.org/manual:installation
3. Harold says:

   11/04/2013 at 06:09

   Can you send me more information on integrating Flyspray as a bug tracking system for Testlink.
4. rjahn says:

   11/04/2013 at 07:51

   Sure, some screenshots are available: http://blog.sibvisions.com/2012/10/10/flyspray-integration-in-testlink/

   What do you need?
5. Harold says:

   02/05/2013 at 21:30

   The source code to bridge Flyspray and Testlink.

   Thanks
6. rjahn says:

   02/05/2013 at 22:44

   The source code is available here: https://github.com/rjahn/flylink
7. Harold says:

   03/05/2013 at 00:05

   Thank you very much!