Linear – A fast issue tracker

Post by doppel » Wed, Jul 01, 2020, 7:14 AM UTC

bachmeier wrote: post #151

jorde wrote: post #19

Earlier quoted context omitted.

We wanted to make the product free for smaller teams to get started without worrying about who to invite. We only count active issue to the limit, and once you're done with them, you can archive them. And yes, we do have support for all users and priority support (faster response times) for paying users. We want to build a long lasting sustainable business and charging for the product is big part of it.

Just to be clear, I wasn't suggesting you should have a better free plan, I was wondering why you have one at all. Free users are expensive and a hassle and I'm skeptical that you'll acquire a lot of paying customers that way. I can't claim to have any idea about the inner workings of this market, though I've spent a lot of time looking at the options in this space. There are plenty of free options for those without…

Post by dpc_pw » Wed, Jul 01, 2020, 7:16 AM UTC

elithrar wrote: post #35

robotresearcher wrote: post #32

Earlier quoted context omitted.

I'm genuinely interested: is this really true? Is Jira necessarily slow when there's a lot of stuff in it? I'm not sure I believe it. There are graph-of-objects-plus-metadata applications out there that are pretty fast. I'm not an expert in this domain, but I bet an issue tracker can be made that doesn't feel painful at real scales.

I didn't interpret the OP to mean slow from an "application performance" perspective - instead, as slow from a "process" perspective. The ticket needs to be filed in the right queue. It needs the "right" tags. It needs to traverse the "approved" workflow correctly. It didn't get assigned to the right epic. etc, etc, etc. It's all of that - the process built up over time, in response to organic needs - that makes thin…

Post by hobofan » Wed, Jul 01, 2020, 7:39 AM UTC

_tbyy wrote: post #55

Hnrobert42 wrote: post #18

Jira is a hot circle of garbage. I am going to check out Linear for my team because I can’t stand how slowly Jira pages load and how long it takes Atlassian to address documented bugs.

Anyone who makes general complaints about Jira like this a) works in a place where Jira has not been correctly configured or b) works in a place with a terrible internet connection c) works in a place where both a) & b) are true or d) doesn't have any idea what they are talking about. P.S. what exactly is "a hot circle of garbage" other than a mixed metaphor?

Post by hobofan » Wed, Jul 01, 2020, 7:42 AM UTC

tommoor wrote: post #155

humanfromearth wrote: post #61

Earlier quoted context omitted.

Same here, I tried Linear, but the fact that it doesn't use github as the source of truth is a deal breaker for us. I would love something like Reviewable - it uses github as the "DB" and provides a nicer interface for doing code reviews.

> the fact that it doesn't use github as the source of truth is a deal breaker for us. Why is that important? You'd be completely hamstrung by the available GitHub API's and speed.

Post by lifeisstillgood » Wed, Jul 01, 2020, 8:06 AM UTC

Benjammer wrote: post #133

LukeShu wrote: post #69

Earlier quoted context omitted.

I understand it to mean that there is a part of the org (separate from the engineering team) that shapes the direction of the product; decides "these are the features we're going to implement, these are the issues we're going to address"; one way of looking at it is that their primary output is putting things in to the engineering team's backlog.

Yeah, this is what I was talking about. Software product management as a separate functional org from engineering. Not like old-Dupont-style product orgs.