111–120 of 230 posts
For many that may find it interesting, here is a recent conversation I had with Linear co-founder Tuomas Artman about how they iterated by listening to their users: https://www.heraldhq.com/userstand/how-linear-leverages-thei...
Looks a bit broken on Firefox.
Day to day I've found myself going from 2+ hours in Jira a day, to Plus I actually love jumping into Linear to catch up on things, whereas Jira genuinely Brough anxiety.
Happy to answer any questions people may have.
Earlier quoted context omitted.
What's your question here? The premise of the OP is that they created a fast issue tracker. 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.
The comment I replied to said that trackers are slow because they are full of stuff, and when you try a new tracker it feels fast because of lack of stuff.
I don't think he literally meant that the app's performance was slowed down by the volume of tickets. I don't think Jira's performance gets much worse even with 10,000s of tickets in it.
The baseline performance of the web app is just baseline bad though.
Founder 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…
Good old Fog Bugz used to have that.
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…
Earlier quoted context omitted.
Looking forward to trying out Linear. I'd really love to use a tool with good performance and offline support! Your website looks slick and lovely too. Alas, the e-mail sign up seems to take a while to send the registration link e-mail. When I got the e-mail after maybe 5-10 minutes of waiting, the sign up link had already expired. :( It says "Verification code expired. Please request a new one." I did, but the same…
Sorry about that! It should work now. We had some issues (and wondering if Gmail is having issues) with emails today. We rolled a fix that increased token expiration and currently looking our email provider if there are things we can do to speed it up.
Earlier quoted context omitted.
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.
you are self-hosted, which is different from cloud.
Earlier quoted context omitted.
The comment I replied to said that trackers are slow because they are full of stuff, and when you try a new tracker it feels fast because of lack of stuff.
I think you might be misinterpreting him. When I read that, "full of stuff" meant old tickets, process that you had to go to, etc. Slow =/= app performance but general cruft. I don't think he literally meant that the app's performance was slowed down by the volume of tickets. I don't think Jira's performance gets much worse even with 10,000s of tickets in it. The baseline performance of the web app is just baseline b…
"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 piled up in the old one. Don't migrate your backlog, start with only a couple engineers in a new issue tracker, and suddenly, wow!, this new tool is so much better!"
I guess it can be read either way.
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…
The other problem cycle is “we’ll get JIRA right this time”. This is followed by happy clicky people immediately shafting it, at least two years of suffering and then some PM selling some new clothes to the emperor. Everything degrades this way. Even GitHub the moment someone adds workflow automation. Intent versus causality are two very different things.
My favourite problem is a JIRA instance that sets a resolution as incomplete immediately on a ticket, which is a valid resolution so all my tickets are closed as far as it’s concerned. Ugh.
I’m slowly working on an OSS replacement for all of this hell which is designed for inflexibility from an organisational perspective. It’ll be open source. I’m sure no one will use it because it’s inflexible.