Show HN: Tara – A smart and free alternative to Jira
One thing that bugs me with development workflow tools is how they never really integrate with the <i>true</i> workflow of developers. Once you have a development workflow with Pull Requests, Code reviews, QA etc, it would be nice to be able to encode it into the<p>What's the true progress of an issue (ticket, work item...)? Why do I need to remember to set a ticket to "resolved" after a PR completes, and so on.<p>Every place has a different workflow and they are usually very complex, but these tools (Jira, YouTrack, GitHub issues, Azure DevOps, ...) <i>are</i> complex. They <i>are</i> often configurable, yet they still (as far as I'm aware) fail to integrate the process part of things with the code part of things. At best you have some loose integration between version control and process e.g. "this ticket has these changes" but they don't integrate the two processes so that the state-machine that is a ticket (is it done? why is it not? is it because a PR build failed? Is it because an approval that must be done after merge has failed? is it because the issue has several pull requests associated with it and not all are merged yet?).<p>I absolutely don't mind complexity in these tools. Having an extremely simple post-it process is good. This is the second best. The process complexity in big enterprises and distributed teams <i>will always be there</i>. If I can configure a tool to make it go away I'm glad. The worst situation is when you have a hyper complicated process and no tools to help. That's the situation many businesses are in. "You didn't mark the two fields and change the state to Y and then send the email to the translation person and notify the regional development person about the change! You have to do that".