Live data from Hacker News

Linear – A fast issue tracker

linear.app

21–30 of 230 posts

Re: Linear – A fast issue tracker

#23
post #14

Using any ticket/bug/issue tracker is better than not using one. That said, much of the information you put in one of these is really sensitive, perhaps even confidential and quite often embarrassing if leaked. So. Privacy policy? Extremely generic, and doesn't guarantee you anything. Terms of Service? "We take no responsibility and assume no liability for Content you or any third party posts on or through Service. H…

I'm pretty sure that's bog-standard EULA for "We need to show the tickets you made to other users on your team."

Re: Linear – A fast issue tracker

#26
post #14

Using any ticket/bug/issue tracker is better than not using one. That said, much of the information you put in one of these is really sensitive, perhaps even confidential and quite often embarrassing if leaked. So. Privacy policy? Extremely generic, and doesn't guarantee you anything. Terms of Service? "We take no responsibility and assume no liability for Content you or any third party posts on or through Service. H…

Thanks, we'll be updating our ToS soon and addressing this feedback. We take user privacy and security extremely seriously (many of us worked at Coinbase) and would never expose anything without your consent. I think this clause was for potentially opting into public sharing but it's not something we do.

Re: Linear – A fast issue tracker

#29
post #21

Is there any CLI interface?

Not yet but we had few people hacking on our GraphQL API already so hopefully we'll get there soon. Integrating into your existing workflow is one of the design cornerstones for us, we don't want to waste anyone's time.

https://docs.linear.app/API-Webhooks-d7b411ffab7b4a91853d04a...

Re: Linear – A fast issue tracker

#30
post #3

We've been using Linear for a couple months. It's kind of like Superhuman in that the primary benefit is hotkeys. Otherwise it is an issue tracker. I think the reason we see a steady stream of new issue trackers is that teams are trying to fix with software what are people problems. New issue trackers feel faster for the same reason switching browsers tends to feel faster—you're getting rid of all of the crap you pil…

I tend to agree but I have a anecdotal counterexample. We recently switched from JIRA to Clubhouse by importing our history and backlog wholesale. Due to the substantial performance bump we have definitively leveled up as a team.

Status updates that used to happen in slack channels are now captured in Clubhouse, people log in to check on progress, stories get love and details.

JIRA cloud was unusably slow and as a result we didn’t want to use the tool. We hated it even though it technically “worked”.

Post reply on HN