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

Linear.app

linear.app

Post reply on HN
Print view View original

61–70 of 132 posts

Re: Linear.app

#61

Post by xwowsersx »

CPLNTN wrote: post #58
xwowsersx wrote: post #32

Anyone using linear without the rest of their team adopting it yet? Obviously the full benefits will only be realized when everyone is using it, but I'm still curious to hear if people are benefitting from using it to manage their own work.

I work with two long term clients (one has two projects going on, the other three), plus I have my own personal projects. Linear has become a vital part of my workflow. The first thing is that splitting tasks by teams (client 1, client 2, and me) and then by project for each team allows me to do some neat stuff: 1. I have a global view, where i can see the status of each single ticket. I use this because when I’m sel…

Thanks for sharing, that's helpful. I'm also using multiple trello boards to manage my own work while our team uses Jira (which is awful).

Re: Linear.app

#62

Post by kotlin2 »

I get the appeal of ticketing, I really do. But ultimately, it's a form of control. ICs can't be trusted to figure out what to do on their own, and can't be bothered to talk their team for guidance. And management needs dashboards to track progress. I get it. But I don't want to work on a team where such things are necessary.

Re: Linear.app

#63

Post by aetherspawn »

OK, we are firmware developers who use JIRA in a very advanced way with our clients, and we gave it a go and I just came back here to give the team some feedback because no doubt they are watching this very closely.

The killer missing feature for us is that we can't define different issue types. For example, we would typically have issue types like "Requirement", "Bug", "Signal", etc. with different icons and use child/parent hierarchies to sort these in a tree with this hierarchy: L1 high-level business requirement, L2 technical breakdown stories, L3 very specific requirement/bug/signal.

In line with this, there's no way to show the issue layout as an expandable tree-view (called "List" view in JIRA), and so our requirements tree would get all mashed up and flattened.

For each technical story/signal we would have a custom field where we set the source file where we are implementing it. This would help us hammer out the architecture of projects very quickly and have them line-up with technical requirements. Doesn't seem to be a way to add custom fields to different issue types. Later we would export this all out of JIRA to help write our documentation.

Lastly, a JIRA replacement without a corresponding Confluence replacement could be a bit of a point of friction. I hope that somewhere on your roadmap you plan to develop a basic solution to cater for the Confluence need.

Otherwise ... it looks nice. Have you thought about offering a self-hosted version, since JIRA no longer offers this?

Re: Linear.app

#64

Post by throw123123123 »

mayoff wrote: post #31

I guess some people spend so much time in Jira or whatever that they want keyboard shortcuts for everything? My company uses Jira and I'm a developer and I've never felt like “oh my god I'm wasting so much time mousing around in Jira”.

It probably depends on setups, but at Robinhood, Jira would take 15 seconds to load a wiki page (any wiki page)

Re: Linear.app

#65

Post by prange »

kotlin2 wrote: post #62

I get the appeal of ticketing, I really do. But ultimately, it's a form of control. ICs can't be trusted to figure out what to do on their own, and can't be bothered to talk their team for guidance. And management needs dashboards to track progress. I get it. But I don't want to work on a team where such things are necessary.

It’s not as simple as that. ‘Talking’ doesn’t create a reference where you can see what’s been done yet, and of course people leave teams or get sick etc. so there are many reasons to want to see what was and wasn’t completed.

Re: Linear.app

#66

Post by rjzzleep »

aetherspawn wrote: post #63

OK, we are firmware developers who use JIRA in a very advanced way with our clients, and we gave it a go and I just came back here to give the team some feedback because no doubt they are watching this very closely. The killer missing feature for us is that we can't define different issue types. For example, we would typically have issue types like "Requirement", "Bug", "Signal", etc. with different icons and use chi…

When you say very advanced way do you mean Jira workflows? Or do you mean more than that?

Re: Linear.app

#67

Post by eru »

kotlin2 wrote: post #62

I get the appeal of ticketing, I really do. But ultimately, it's a form of control. ICs can't be trusted to figure out what to do on their own, and can't be bothered to talk their team for guidance. And management needs dashboards to track progress. I get it. But I don't want to work on a team where such things are necessary.

As your organisation get bigger some structure and bureaucracy is necessary and beneficial.

Of course, whether that structure and bureaucracy needs to be a ticketing system is a different question.

Re: Linear.app

#68

Post by eru »

prange wrote: post #65
kotlin2 wrote: post #62

I get the appeal of ticketing, I really do. But ultimately, it's a form of control. ICs can't be trusted to figure out what to do on their own, and can't be bothered to talk their team for guidance. And management needs dashboards to track progress. I get it. But I don't want to work on a team where such things are necessary.

It’s not as simple as that. ‘Talking’ doesn’t create a reference where you can see what’s been done yet, and of course people leave teams or get sick etc. so there are many reasons to want to see what was and wasn’t completed.

On a small enough scale, 'talking' does work. So do post-its etc.

If kotlin2 sticks to those small enough scales, they can indulge their preferences.

Bigger organisations have more and more need for structure.

Re: Linear.app

#69

Post by inquirer39243 »

enra wrote: post #7

Karri (cofounder) from Linear here. Unfortunately we have been experiencing a DDoS attack the whole afternoon today, so the service is not optimal at the moment and the public website might be slow to load. We are actively blocking and mitigating the attack. https://linearstatus.com Sidenote: While we had these issues, we decided to redirect our homepage to our website Figma file, where we shared iterations for the d…

I couldn't find a mention of it - but is there any plans or ability to self-host? I'm personally not a fan of keeping everything in the cloud. Also are there export options in the event someone wanted to leave the platform?

Re: Linear.app

#70

Post by tkk23 »

jorde wrote: post #21
dawnerd wrote: post #11

so question if someone from Linear is reading these, which I assume they are: The site says shortcuts for everything. That's nice. But one of my biggest gripes is accidental actions with no indication on what you just did. If I have the app open in one window and don't realize I have focus and just start typing will it just start doing actions? Is there a way to disable these? Clickup does this to me a lot and its su…

We implement undo through Cmd+z

That's a fix but doesn't give you the feedback about what you just did.
Post reply on HN