Live data from Hacker News

Linear.app

linear.app

91–100 of 132 posts

Re: Linear.app

#91
I spend all day in Linear and really love it! Thanks for your quick response to the ddos today, it was a nice opportunity to brew some coffee :)

I run a team that sits between Support and Engineering, bug reports from the highest tiers of support are written up as issues and submitted to our triage. We investigate the issues to find root causes, determine the parties best situated to resolve them, assess user impact, add appropriate labels, and then move them to the triage of the appropriate team's space.

The biggest limitation we've run into is adding metadata to our issues: labels are great, but when you transfer to another team you lose labels or have to add clutter to that team's set of chosen labels.

I've ended up building some tooling on top of Linear to record things like user impact assessment data. This tooling posts the data back into the issue as a formatted comment so it's visible inline, but we can query it directly in our database and build metrics off of it. This approach has really opened Linear up for us. Thanks for the graphQL end point, it's been very helpful!

Re: Linear.app

#92
I have used Linear on a couple of my hobby projects and it's a great tool to quickly capture features and bugs.

My one gripe about the new website (and it's something I notice many projects stumble at) is that the written copy fails to explain what the product actually is. "A better way to build products", "the new standard for software development", "a tool to remove barriers" -- this tells me nothing, unlike a simple "it's an issue tracker bro" would.

Re: Linear.app

#93
post #90

OK, we are firmware developers who use JIRA in a very advanced way with our clients, and we gave it a go and I just came back here to give the team some feedback because no doubt they are watching this very closely. 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 chi…

Wouldn't tags for for this? It's similar to how I use them.

We could use tags for this, but with an issue type hierarchy you can strongly-type your database i.e. make sure that people don't put a Signal under a high-level business requirement.

And different issue types in JIRA allows us to have different workflows and optional fields for different types of issues, ie in the use-case above the Requirement field has an extra field to mention a corresponding document and most of the issue types except business requirement have an extra field to fill in the source file where we will implement it.

Re: Linear.app

#94
post #81

OK, we are firmware developers who use JIRA in a very advanced way with our clients, and we gave it a go and I just came back here to give the team some feedback because no doubt they are watching this very closely. 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 chi…

> 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 u…

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.

Re: Linear.app

#95

OK, we are firmware developers who use JIRA in a very advanced way with our clients, and we gave it a go and I just came back here to give the team some feedback because no doubt they are watching this very closely. 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 chi…

I honestly despise Confluence. Jira is kind of OK if you don't create overly complex workflow (they will fail) and avoid using it as a documentation tool (it's not versioned, editing tool are lacking, adding content is quite limited, updating content while fighting field is not fun and finding back the last CR related to a feature is hell). But Confluence is the worst Wiki I've ever used. It's editor is obnoxious, it…

They've (recently?) introduced a feature where they disable the editor window in Confluence if the browser even momentarily loses the network connection. On a poor network it's absolutely unusable now.

Re: Linear.app

#96
We are really happy customers of Linear and have nothing but good things to say about it. Product is light and snappy, customisable just in the right amount and UI/UX is very predictable.

Biggest weakness is definitely the "workflow" part. For example, trying to automate rather simple workflow that involves email to ticket isn't trivial and either requires you writing your own integration or passing via something like Zapier (or writing your own integration with Zapier?).

Re: Linear.app

#97

Reading through the comments it appears more than 10 employees of linear are dominating 33 comments. Sorta seems like this is marketing at its sneakiest.

Seems unlikely it is sneaky marketing considering this was posted to HN right as they were in the middle of a multi-hour DDoS.

My guess is that they are excited about their product being on here.

Re: Linear.app

#98
I've tried it recently, since it markets itself as being performant, and native-like performance is what other popular tools like Jira or Trello miss. I want to say upfront that 50ms user interactions is not what I would consider "breathtakingly fast" as the website claims. It's much better than the tools mentioned above, but doesn't really cut it for me. Maybe I'm old, but I see lots of unnecessary animations, that (in my opinion) contribute massively to the perceived slowness of basic interactions. Some of the animations are not that smooth at all, e.g. the new issue label menu color dots jiggle when menu animation finishes. I'm so tired of seeing marketing speak like "UI elegance with world-class performance" to then be only disappointed in the difference between my and the author's views on what "performance" means.

Feature-wise Linear looks great though, so I might give it another try in some time.

P.S. Can someone please explain the hate for the pointer cursor? Why some products refuse to use it for links and buttons?

edit: I reread my comment and found it sounding a bit too critical. I really think that Linear is much better that most of the alternatives in the regard of UI/performance. It's just that I hate how the meaning of the word "performance" devalued with time and claims like "50ms = breathtakingly fast/world-class" continue to contribute to that.

Re: Linear.app

#99
post #98

I've tried it recently, since it markets itself as being performant, and native-like performance is what other popular tools like Jira or Trello miss. I want to say upfront that 50ms user interactions is not what I would consider "breathtakingly fast" as the website claims. It's much better than the tools mentioned above, but doesn't really cut it for me. Maybe I'm old, but I see lots of unnecessary animations, that…

From memory there's an option in the settings to enable pointer cursor.

I'd wager they're doing it becuase a pointer cursor feels more like a web browser, and would impede the feeling of the app being native.

Re: Linear.app

#100
post #98

I've tried it recently, since it markets itself as being performant, and native-like performance is what other popular tools like Jira or Trello miss. I want to say upfront that 50ms user interactions is not what I would consider "breathtakingly fast" as the website claims. It's much better than the tools mentioned above, but doesn't really cut it for me. Maybe I'm old, but I see lots of unnecessary animations, that…

I agree, it's quite ridiculous to call that performant when considering the reality of what's possible. But compared to other electron apps, it's way better, and the team has done a good job with the bad tools given. I suppose the bar isn't very high when it comes to performance, but it's a nice positive signal that it's used as a marketing point like that. Although you do point out that the expectations are often like from two different worlds, which is true. I guess it leaves room for competent competitors.
Post reply on HN