Sometimes, tools like linear... don't quite give you the flexibility and cross-integration you desire.

I get to use all the bells and whistles SaaS products like linear, sometimes I think it's cool that the tool will do something like point out I'm about to create a duplicate ticket.

Linear's big innovation was taking issue tracking and giving it a polished UI/UX. And guess what? People love it are buying it.

also using linear for issue tracking. They’ve been launching some cool stuff for agent integrations.

Linear does an extraordinary number of useful things beyond issue list.

I could track issues in linear... but only by manually moving text from one place to another, manually moving the tickets.

For really big features or plans I’ll ask the agent to create linear issue tickets to track progress for each phase over multiple sessions.

For my hobby projects, I've been using Linear + agentFlavorOfTheMonth quite happily this way.

Other integrations with Linear and Slack are also very handy to getting into this workflow.

We've set up a linear integration where I can delegate simpler tasks to cloud agents, and the ability to pick that work up in cursor if I need to go back and forth is a real productivity boost.

The tech we've chosen, and the actual app itself, essentially _feels_ like Linear for email.

my experiences on teams that use something simpler like Linear because the tool kind of guides you toward sane behaviors instead of letting you go nuts.

Most work-planning tools today (Jira, Linear, etc.) are DB-centric and form-driven, which makes them awkward for agentic workflows.

They do this so that they can iterate on them in a more collaborative place vs Jira Linear. It's a bit annoying for eng to have to parse thru the spec to map requirements for a specific ticket.

Linear isn't opinionated. Rather, it's a Jira-like describe how your company's workflow should into the app one CRUD object at a time tool.

The sentiment is incredibly high on Flow and Speed, but the analysis flagged a legitimate gap in Enterprise Reporting.

We actually switched from Linear to Github Issues because of how nice it is to have the TODOs colocated with PRs and code.

Even scrolling through the features page, I couldn't figure out what the actual core product was, until I gave up and went to the github page and immediately found the answer. (It's an issue tracker)

Linear was just OK to me and none of these sync features seemed to raise it above any other issue tracker I've used. With the added downside that loading the workspace from the pub via the webapp could be excruciatingly slow.

Link your exceptions to your project tracker, so you can create Jira, Linear, etc. tickets directly from exceptions in Sentry.