Hacker News Reader

Comment by meowface | Hacker News Reader

I'm sometimes kind of surprised at how often I see people say they don't mind it. It's by far the tool I like the least out of everything I've used at any job I've ever been in.

View on HN

I don't mind it. Maybe because I only peek into it about once per week or so, so we don't really drive daily work using it.

Same, I check into Jira once per day, max. It's useful to give an overview of what everyone is working on in the "Kanban" meetings twice weekly. I use quotes because we really don't follow any strict rules or structures, everyone just kind of does what needs to be done to keep things moving forward.

Maybe a couple times a day for me, but mostly if I somehow have two things going at once.

Meanwhile I’m battling Bamboo regularly, and I hate everyone who has ever worked on that crime against humanity.

It's a tool for the boring part of software engineering- I don't expect it to spark joy. I wish it were faster, scaled the full width of my monitor, allowed external editors, etc. Overall it gets the job done well. Everything else that I've used is horrible which makes it the best in my experience but that's still not saying much.

But what if it _did_ spark joy… https://linear.app/readme

We use Linear at my job too - it's very smooth and easy to use and certainly does spark joy

This looks really nice but it scares me to think of what my large (60,000+ employees) employer would do to it. Thanks for sharing though- I'm going to check this out.

I use linear and I hate it more than jira. It’s jira with all the useful production features removed, making it useless for large teams and qa teams. Beyond simple task tracking it has been a chore to use.

We use it at my current work and I'm not impressed. We even moved back some workflow steps to Notion because of lost work in the editor.

Frankly, I miss the limited GitHub PM tools we used at my previous job.

Even their one true limitation, no sub-issues, is very meh on Linear.

I looked it over, but the properties provided prevent us from organizing and prioritizing the tickets on things that matter to us. Doesn't look like we can add properties to issues.

So, if we have some kinda numerical metric, call it "foo", we can't ask linear to give us all foo's over 6.

So if we wanted to do any kinda metrics, basically, we have to export our whole project as CSV and do the calculations there? I just checked the export system. It exports everything only. I don't think this is tenable for project management.

I can see it work for a personal task list or a small team doing simple sprints. But... I wouldn't see it used beyond that.

Maybe I'm off base on all this, I did just give the product a quick once over. If I missed ways to make all this work, then that's on me.

I only use Jira for defect tracking and not project planning. In that regard it seems to be only slightly worse than Github/Gitlab's issue tracking. It'd be kinda nice if it supported Markdown but it's not a big deal.

The only things I need it to do are: (1) record an archive of comments describing the progress on the issue's resolution, (2) be able to store attachments, (3) be able to cross-reference other issues. Maybe I have a really low bar? But it seems to do those without much problem and in my case it doesn't seem to be slow.

I would fight you about how Bamboo is the worst tool I’ve had to use, but since they’re both from Atlassian that feels a bit like splitting hairs.

The UX is annoying as hell but I am almost never unable to do what I need to do. I can't say that for all SaaS tools.

There's lots of worse shit here: https://en.wikipedia.org/wiki/List_of_version-control_softwa.... I remember IBM ClearCase in particular as vile.

Only if you toss in multi-site for fun. :)

It's quite easy to have a minimized exposure to jira as a developer. I hate its guts but if my interactions are limited to writing a few tickets and changing statuses then its awfulness is more somebody else's problem and it doesnt bother me nearly as much.

I don't love it, but I sure hate it less than just about everything that came before it.

I'd prefer any kanban board app over jira.

If it's set up properly, it's easy for developers to browse the tickets, log work on them, and update their status - and that's all they will need to do. So, from their perspective, it's fine. However, getting to that point is unnecessarily difficult, and if you fail, that difficulty spills over into the developer experience.

Jira is terrible until you try other tools for managing dev work.

What tools do you like the most?

Reply on news.ycombinator.com