I make heavy use of the `fixes #` feature on Github to auto-close issues. This adds up over one or two years when you're closing multiple issues per week.
Linear – A fast issue tracker
51–60 of 230 posts
Re: Linear – A fast issue tracker
#52We'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'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.
Re: Linear – A fast issue tracker
#53Using 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."
"We keep the data that you store with us confidential. Our staff will not look at it unless you specifically ask us to investigate a specific issue. Other than legal requirements (e.g. a valid subpoena) we won't share it with anyone unless you've identified them to us as part of your team or otherwise authorized to see your data."
You should always say what you mean in contracts.
Re: Linear – A fast issue tracker
#54Earlier quoted context omitted.
> 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”. - every JIRA customer ever
We're a JIRA customer and we're quite happy. It's not slow, at least to any degree that matters. We're not a huge team, nor do use much more than tickets with FishEye integration though. We also have a self-hosted instance. But for us it has worked quite well, and I have better memories of JIRA than say MantisBT which I used before.
Re: Linear – A fast issue tracker
#55Jira 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.
Re: Linear – A fast issue tracker
#56https://www.joelonsoftware.com/2000/11/08/painless-bug-track...
But cool as it looks, I'm personally reluctant about replacing my locally hosted open source developer tools by pay-per-month SaaS solutions which are closed-source and handle possibly sensitive data of me and my customers.
Re: Linear – A fast issue tracker
#57Founder here. Here to answer any questions you might have. We built Linear as we’re frustrated the practices and the available tools when it came to managing software projects. On the product, we especially tackled the performance problem. Everything is synced to the client and we sync just delta packages between the cloud and client as changes happen. This way all actions a happen instantly and navigating around the…
Hello. Looks good on the screenshots, I'd love to try it for my team but the signup link somehow sends me to Google instead of signup. /s How do I try it? On a side note, I use Edge on a Mac and the signup page doesn't detect my browser as compatible; it's just Chromium inside, must be totally compatible with everything.
On browser detection, we need to look at Edge. I don't think we updated the list in a while (we support all evergreen browsers).
Re: Linear – A fast issue tracker
#58Earlier quoted context omitted.
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 re…
I haven't noticed JIRA cloud being that slow, but maybe that's because the team is small. Did you start to experience performance issues as team size increased? Did you have a lot of issues or data held in the issues? Or was there another issue that you think led to the slowness? I'm interested in your insights as we went with JIRA initially, since it was pretty much the gold standard and we thought it would scale ni…
In my case, we were a small team (<10 users, <1k total issues split in maybe 8 projects), and were running into random load time slowness irritations. It never stopped us from doing what we needed to do, but it sure did make it more frustrating to do it. We are using a cloud instance.
Re: Linear – A fast issue tracker
#59We'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'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.
People complain about Jira being slow (me being one of them.) No one has claimed that all issue trackers are slow. ClickUp, Hive, Linear, are all snappy.
Re: Linear – A fast issue tracker
#60Jira 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?