<story><title>Plane: Open-Source Alternative to Jira</title><url>https://github.com/makeplane/plane</url></story><parent_chain><item><author>bipson</author><text>The Problem with Jira is not that it&amp;#x27;s dumb or too sophisticated.&lt;p&gt;The first problem is that everyone, even in the same team or org, needs something different from it. Sometimes it is even single individuals needing one particular thing one time, and the same day for another workflow or view another thing. It is when Jira caters to the wrong use case for you &lt;i&gt;right now&lt;/i&gt; where the a lot of frustration arises.&lt;p&gt;In a similar vein, it wants to cater devs, coaches, POs, business people, customers and all of them over various orgs with drastically different workflows. Serving everyone equally must lead to a mediocre experience. You will always miss something, while there is so much stuff you don&amp;#x27;t need or want and you have to work around.&lt;p&gt;Arguably, this has become better a lot in the last 10 years, but you will always long for &amp;quot;something better&amp;quot;.&lt;p&gt;But the most painful issue is that in some orgs Jira &lt;i&gt;is&lt;/i&gt; the workflow, instead of supporting it and staying in the background. At some point people are only sending around ticket links, commenting on tickets, requesting people monitoring their queues. This creates overhead, redirection and Jira becomes a distraction you need to handle.&lt;p&gt;As a result Jira becomes a proxy for all the things going wrong with your daily work and a problem of its own.</text></item></parent_chain><comment><author>mark_and_sweep</author><text>The biggest issue, in my experience, has always been its performance. Perhaps I have only worked in organisations that have completely misconfigured their Jira instances or the servers are underpowered, but even with the Atlassian Cloud, I am used to waiting 10 seconds to move a ticket from one column to another. Or add a ticket to the backlog, click the backlog, ticket isn&amp;#x27;t there yet, refresh the backlog, it&amp;#x27;s there. Add a ticket to the sprint, click the sprint view, ticket isn&amp;#x27;t there. Refresh the sprint view, it&amp;#x27;s there. This sh*t. Every day. Is driving me insane.&lt;p&gt;I don&amp;#x27;t want the perfect tool, just one that isn&amp;#x27;t horrendous.</text></comment>
<story><title>Plane: Open-Source Alternative to Jira</title><url>https://github.com/makeplane/plane</url></story><parent_chain><item><author>bipson</author><text>The Problem with Jira is not that it&amp;#x27;s dumb or too sophisticated.&lt;p&gt;The first problem is that everyone, even in the same team or org, needs something different from it. Sometimes it is even single individuals needing one particular thing one time, and the same day for another workflow or view another thing. It is when Jira caters to the wrong use case for you &lt;i&gt;right now&lt;/i&gt; where the a lot of frustration arises.&lt;p&gt;In a similar vein, it wants to cater devs, coaches, POs, business people, customers and all of them over various orgs with drastically different workflows. Serving everyone equally must lead to a mediocre experience. You will always miss something, while there is so much stuff you don&amp;#x27;t need or want and you have to work around.&lt;p&gt;Arguably, this has become better a lot in the last 10 years, but you will always long for &amp;quot;something better&amp;quot;.&lt;p&gt;But the most painful issue is that in some orgs Jira &lt;i&gt;is&lt;/i&gt; the workflow, instead of supporting it and staying in the background. At some point people are only sending around ticket links, commenting on tickets, requesting people monitoring their queues. This creates overhead, redirection and Jira becomes a distraction you need to handle.&lt;p&gt;As a result Jira becomes a proxy for all the things going wrong with your daily work and a problem of its own.</text></item></parent_chain><comment><author>zelphirkalt</author><text>Catering to many different kinds of people explains some of the bad stuff, but it does not explain, why seemingly every single Atlassian product including Jira sucks at parsing Markdown or supporting Markdown well. In the big picture maybe some things suffer from catering to too many audiences, but in the small, it is just lack of good engineering. Basically any markdown parser you can install at no cost and even with pushover license for any popular programming language works better than what they cobbled together. Is it a case of some &amp;quot;senior&amp;quot; person sitting somewhere sheltering their brain child?&lt;p&gt;Also they seem to be immune to feedback, which they wanted to collect in Confluence, using some popups.</text></comment>