Leantime: Open-Source Jira Alternative
I keep looking at various JIRA alternatives, but no good finds so far.  This is definitely not it.<p>I don&#x27;t really like the idea of bug tracker as a sort of a GUI program that acts like time management software, i.e. focuses on planning work, tracking how much effort was spent, ability to add notes to tasks etc.<p>My ideal bug-tracking software works more like Git: it has a server-client relationship where clients query the database with predefined set of commands, while at the same time it has programmable interface facing test code.  This interface should enable tests to do things like:<p>* figure out what components need tests to run against them when a particular feature branch sees a code update.<p>* extract history of tests running against a defined group of features.<p>* manage association of tests and program components.<p>* manage test sets that aren&#x27;t feature-related (eg. nightlies).<p>JIRA kind of has this database &#x2F; query component, but all the functionality above needs to be built on top of it.  And the data organization of JIRA relies on issues as the basic unit, where I&#x27;d like the basic component to be &quot;features&quot; (similar to how branches are in Git).<p>My biggest problem with the currently popular approach (emphasis on time management) is that it&#x27;s very informal and unstructured when it comes to testing, poorly automated and poorly integrated with other development tools to the point that it makes it both easy to forget to do the necessary stuff and a very repetitive chore to keep the necessary stuff up-to-date, while it&#x27;s clear that it&#x27;s possible to automate it.<p>The attempts to automate this process by adding bots that manage issue life-cycle or generate trivial fixes &#x2F; merge trivial PRs isn&#x27;t the way to solve the problem, IMO because this automation is stupid and has a potential to cause harm.  Instead it needs to be very tightly integrated with VCS (but, let&#x27;s be honest, with Git) to the point that such configuration would require minimal effort on the part of the admin and be vendor-independent, and, most importantly, be feature-oriented to mirror how programmers conceptualize the development of their program.