Open Source Issue Trackers

“Open source issue tracker” describes several different products: focused trackers, project-management suites and issue systems attached to source hosting. License and edition model matter as much as the feature list.

The landscape

Start by deciding whether issues are the product’s center or one module in a larger suite.

  • Focused and agile tools: Kuayle, Plane, and Taiga — issue workflows and sprint or cycle planning
  • All-in-one PM: Redmine, OpenProject, Leantime — broader scope with Gantt, wikis, time tracking
  • Platform-embedded: GitLab Issues, Gitea, Gogs — tracking alongside source code hosting

Licensing differences

Source availability does not make licenses interchangeable. Permissive licenses and copyleft licenses impose different redistribution obligations, while some vendors maintain paid editions or features alongside a public repository.

  • Apache 2.0: Kuayle — permits commercial use and modification subject to license conditions
  • Copyleft projects use licenses such as AGPL or GPL; review each project’s current license and obligations
  • Open core: some tools offer basic features as open source with paid enterprise add-ons

Where Kuayle fits

Kuayle is a focused, self-hosted issue tracker rather than a general project-management suite. Its current application and deployment code live in one Apache 2.0 repository, with no enterprise edition or license-key path.

  • Multiple assignees on one issue
  • Keyboard shortcuts and issue search
  • Cycles, projects and GitHub automation
  • Reference Docker Compose deployment

Sources

Licenses and editions change. Verify them in each project’s first-party repository or documentation.

Review Kuayle before you deploy it

Inspect the Apache 2.0 source, then follow the Docker Compose guide to run an instance on your infrastructure.