[lmm]

> The killer missing feature for us is that we can't define different issue types. For example, we would typically have issue types like "Requirement", "Bug", "Signal", etc. with different icons and use child/parent hierarchies to sort these in a tree with this hierarchy: L1 high-level business requirement, L2 technical breakdown stories, L3 very specific requirement/bug/signal.

Support for this kind of overcomplex use case is what makes JIRA so horrible to use. I very much hope Linear never bloats itself by adding this kind of thing.

[aetherspawn]

You'd better hope that enough people need a very barebones tracker (thousands of barebone trackers exist) enough to pay for it and keep it alive. Or you can implement the "overcomplex use case"(s) and create a product that is actually more useful than those other thousand of issue trackers built-in to tools that people already use.

[solardev]

Hell no. If you want jira, use Jira. Linear is better specifically because it's not Jira and doesn't try to be.

A huge part of its appeal is that it actively prevents workflows like yours. On purpose.