Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Linear – A fast issue tracker

linear.app

Post reply on HN
Print view View original

71–80 of 230 posts

Re: Linear – A fast issue tracker

#71

Post by mdeeks »

enra wrote: post #9

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…

One of the common workflows for us with Jira is to search for things that have changed in the last day

  status changed during (-1d, now())
That lets me as a manager or a lead, see activity in their project and know when engineers update their tickets with details or comments. Is there a way to do that with Linear?

For all the hate that Jira (deservedly) gets, its search is extremely powerful. Maybe it's best feature. I'm not sure how well Linear would scale for a larger org of hundreds of engineers, dozens of teams, and tens of thousands of tickets without similar search abilities. Any roadmap plans for that?

Re: Linear – A fast issue tracker

#72

Post by gnud »

ocdtrekkie wrote: post #39

I have a rough time understanding why I'd pick this over the issue tracker integrated with my source control. I get that it can sync with GitHub or GitLab (Does it sync the issue text/comments such that GitHub users can comment on the issues? Are the issues on both sides using the same numbering? In this case, is Linear just a GitHub issues client?) but I imagine I am losing out on any given feature that my source co…

You don't want your issue tracker in your source control if your product includes multiple source repositories, and a single bug might span several, or need to move between them.

Also, if you have customers who file bugs, they don't care about your code structure. And maybe they shouldn't have read access to your code?

Re: Linear – A fast issue tracker

#73

Post by plainOldText »

I haven’t tried Linear, but while browsing the site I couldn’t help but notice what an exquisite job the designer did with the Linear site.

It’s consistent, lightweight, it has pleasant proportions, a nice color theme, etc. It’s also sprinkled with all kinds of little details that show care, attention and craftsmanship.

I wish I’d see more sites like this.

Re: Linear – A fast issue tracker

#74

Post by heavenlyblue »

grk wrote: post #60
_tbyy wrote: post #55

Earlier quoted context omitted.

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?

So cloud hosted Jira is misconfigured?

I would assume they mean “you have not set up your JIRA workflow according to your needs”

Re: Linear – A fast issue tracker

#75

Post by jnwatson »

ChrisMarshallNY wrote: post #46
tbrock wrote: post #30

Earlier 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 was a JIRA admin for a number of years for an organization that had a heavy QA workflow. It was all about making sure that every issue had an "owner," at any given time, a strict approval and verification process was followed, and that as much up-front data as possible was collected during the initial report. In my experience, unless the people entering the issues are paid, professional engineers, we'll never get t…

In my experience, it isn't Jira that people hate, it is the horrible rules and bureaucracy-ridden workflows that Jira allows an admin to implement.

My team switched back to Jira after trying several other tools and we're pretty happy.

Re: Linear – A fast issue tracker

#76

Post by evaneykelen »

humanfromearth wrote: post #61
olingern wrote: post #51

It would be neat to have Github, Gitlab, etc. mirrored because I've always seen issue software that doesn't directly integrate with repositories to be more work to manage than not. 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.

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.

I’m working on TaskSift which, although it’s not a pure issue tracker, does use a mix of sources like email, github, etc as its source of truth when it comes to issue status.

We struggled quite a bit with getting this status thing right, finally settling for model where user stories inside TaskSift are based on multiple inbound tickets (each with a different status), and where each story can be published eg to GitHub, QA queue, an l10n tool, etc again each with its own status and completion time.

Once all published tasks are finished the folks who contributed to the inbound tickets can all be notified, and the tickets can be closed, either from within TS or using the tool in which the ticket was created originally (Zendesk etc).

Re: Linear – A fast issue tracker

#77

Post by ocdtrekkie »

gnud wrote: post #72
ocdtrekkie wrote: post #39

I have a rough time understanding why I'd pick this over the issue tracker integrated with my source control. I get that it can sync with GitHub or GitLab (Does it sync the issue text/comments such that GitHub users can comment on the issues? Are the issues on both sides using the same numbering? In this case, is Linear just a GitHub issues client?) but I imagine I am losing out on any given feature that my source co…

You don't want your issue tracker in your source control if your product includes multiple source repositories, and a single bug might span several, or need to move between them. Also, if you have customers who file bugs, they don't care about your code structure. And maybe they shouldn't have read access to your code?

Fair points.

Re: Linear – A fast issue tracker

#78

Post by tbrock »

ghshephard wrote: post #68
tbrock wrote: post #30

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

Not sure what happened to you - but speaking anecdotally, but from someone who logs into Jira Cloud every day, and spends 20-30 minutes interacting with the interfaces over 8-10 hours a day, and has done so for the last 3 years - it's had a handful of outages, nothing that really rose to the level of being memorable though (and less than any internal issue tracker I've worked with) - and the performance is, fine? I m…

Ours JIRA instance took multiple seconds to load modals. Think 5+ seconds. It was miserable.

I would have gladly paid more for faster speed but it turned out the APIs were blazing fast and it was the JS that was slow. Not sure how we have had such different experiences. Seems impossible that your JS was executed that much faster than mine. I was using chrome FWIW.

Re: Linear – A fast issue tracker

#79

Post by Lightbody »

We started using Linear a couple weeks ago and overall we're very happy.

There is no doubt that @tyre's points about a "reset" being part of the reason folks like new issue trackers.

But setting aside the "reset" we got (our backlog from other tools wasn't _that_ big), we really enjoyed the speed and accessibility (ex: desktop app, keyboard shortcuts, etc).

I recommend folks give it a try.

My only feedback to the Linear team is: I get notifications for the desktop app to upgrade too often. I love rapid iteration, but it feels like it's daily.

Because I get it so often, it's caused me to start to not pay attention to the "red dot", which my brain has convinced itself is "update ready" and not "unread items in inbox", which it really is.

Hopefully you can find a happy balance or some other UX tricks to help me out here. Thanks!

Post reply on HN