Skip to content
← All posts

Trying an open-source Django bug tracker instead of Jira

  • Django
  • Docker
  • Python
  • Bug Tracker
  • Jira
  • Open Source
  • Dev Journey

Our tickets lived in Jira, so Jira is what we used. We are a small team: 7 developers and 3 QA. That is exactly 10 users, which fits Jira's 10-user limit, but only just. One more person and we would be paying, and by then every ticket we had would be sitting in a tool we could not easily leave.

We did not want to get tied to it. So I went looking, and learned something I should have known already: there are open-source bug trackers written in Python that you can host yourself, instead of using or paying for Jira.

Think Taiga, or lighter options like GlitchTip and django-helpdesk. They are Django apps.

Why self-host a ticket system at all?

It is a fair question. A ticket system is a small line item, and it can simply be covered as part of the development costs.

But this is a freelance setup, and in a freelance setup every cost that can be reduced is important. A subscription that grows with each person you add is exactly the kind of cost worth removing before it starts.

And a small yay on top: these trackers are written in Python, a favorite language of mine. If something needs changing, I can read the code and change it.

A bit old, and that was my worry

Some of these projects are a bit old, and an older Django app is not fun to install straight onto a current Linux machine.

Modern distros block global pip installs with an externally-managed-environment error, and the system Python is often newer than the one the project expects. The database adapter wants system C libraries that need root to install. Then the app and Postgres have to find each other on ports that something else may already be using.

That is an afternoon of setup before you have even seen a login screen, which is a lot to spend on a tool you only want to try.

We tried it with Docker

Docker made it easy to try. The container carries the Python version, the libraries and the database the project wants, so its age stops mattering to the host. Nothing gets installed on the machine itself.

We did not have to write the Docker setup ourselves either. Taiga publishes one, taiga-docker, and that is what we tried. It ran. There were some gotchas along the way, but nothing that stopped us from getting it up and clicking around.

Where we ended up

The bigger problem is not the setup, and it is not Taiga, which is still maintained. It is our own history. All of our previous tasks are in Jira, and that history is going to be hard to let go.

So I think we will switch back to tracking issues with GitHub Projects and issues. It is free, which answers the cost question, and it sits right next to the code.

Trying an open-source alternative cost us very little, thanks to Docker. The hard part of changing a ticket system is not installing the new one. It is leaving your task history behind.