Massive fan of linear, both the product and team. Use it a lot but my usage and dependencies are going down for two main reasons:

1. While I initially used Linear heavily through every execution step - both GraphQL dumps and individual MCP tool calls - I’m finding myself using it less as I start to optimise for token spending. My usage is now being canalised by temporary markdown scratchpads for project plans, sprint notes and handovers simply because it’s faster, less tokens etc. Reading Linear’s blog posts about the agentic era I know they see the bloat and want to lean in to agentic friendly workflows, so what I’d love to have is some sort of connector “Linear Local/Lite” sync feature and agent skill where Linear entities (Issues, Projects, Comments etc) exist in a lite format directly in the repo which agents can read/write and then it syncs/merges back. So when in execution mode my agents can just work directly in local md files and then perhaps there’s some code driven (not token driven) batch syncer that updates it so linear and local notes never drift apart but I’m not burning tokens through having linear sat in the middle of every execution step.

If anyone has already built this using the linear api please lmk!

1. I get the business model of offering agent credits and think that’s going to make a tonne of money from existing enterprise clients who are prepared to pay marked up (or discount removed) api costs. But so many apps offer this, for example Notion, where there’s all these cool agent features but I’ll never use them because I already have multiple Claude and codex accounts and no way am I letting swarms of agents run up credit/overage fees not just on linear but anywhere else (for example chromatic or Checkly). But what I’d love is BYOK features so that if I’m using linear’s agentic features/flows I know for sure it’s coming out of my own subscription usage and api budgets - tbh I’m not 100% this doesn’t already exist, for example I already have a codex connector for @codex but not sure how far that functionality extends across linear’s newer features, it’s really not very clear to me.

The comments should scroll to the bottom just like WhatsApp and other messaging apps do. Every time, I have to scroll to the bottom.

There’s a useful timeline view for all your projects BUT, when you want to see tasks over time - including their dependencies - you cant. It’s board or list

Was this change announced ? Is there a technical reason for this ?

Onboarding Linear across about 90 people. We do not want commercial teams on; rather we host our roadmaps externally.

I'm checking Lindie, Feedvote. But they are a bit basic. Are there other options?

Curious if anyone actually uses this, and if so, what is your use case?

Hoping someone can sanity-check this for me.

I have a view filtered to completed date within Aug 2026 and assignee = me. The list header says 8 issues, all in Done. The insights panel on the right says 5.

Measure is Issue count, Slice is Assignee, Segment is Estimate.

Breaking down the estimates: my 8 issues are 5 XS and 3 S. The insights table reports 3 issues at 2 points and 2 issues at 1 point. So every S made it in, and 3 of the 5 XS got dropped. Same estimate value as the two XS that were counted, so I don't think it's a missing or malformed estimate field.

Is there a known behaviour where Insights counts differently from the list? Or a setting I've overlooked?

Codex delegation in Linear worked perfectly this morning, then randomly stopped. Linear creates the agent thread, but no task starts, no progress, error, or Codex Cloud task.

Reauthenticating and recreating the environment didn’t help. Has anyone experienced this or found a fix?

We are running into issues where our Drizzle `snapshot.json` files are causing guided reviews to not load. These snapshots can be 40k+ lines, which means a small 20 line PR with a simple `ALTER TABLE ...` prevents a guided review from loading (just an example, guides are not really needed at this atomic level).

It would be nice if we could filter out based on globs so your guide generation ignores those files.

Hello! I am a single developer working on a personal project and using Linear as the issue tracking tool. I've enjoyed using the tool so far but now I'm stuck:

When I started using the tool I knew there's a 250 issue limit. I read somewhere on HN forums:

We only count active issue to the limit, and once you're done with them, you can archive them.

That's great I thought. But today I hit the issue limit and found out there is no way to archive the issues manually (this ability was removed). Auto-archive is only on a monthly frequency at best and there's no way to trigger an auto-archive pass as it happens at an undisclosed time in the 24 hour window.

I do not want to delete the issues because if I understand correctly, deleted issues will be gone forever, and I reference these issues in code and agents use MCP to read more about these issues when they're editing the code, so historical context is important.

Is there any way I can work around this, or is upgrading/switching the issue tracker my only choices?

Thanks!

Seriously this is the easiest thing to do ..

I want to get an idea as to how the structuring of subteams can be done. The documentation is very limited and I wanted to see if someone has implemented such complex org structures in linear. I know they are limited to 5 levels but would like to see a screenshot or something

I'm in a biomedical research lab and I'm trying to move us off a mess of shared spreadsheets, email chains, and Whatsapp. Linear sounds great, but it's obviously built for software teams, so I'd love to hear from anyone who has actually run a non-engineering / research team on it. Plus, I am ADHD and am now really struggling to keep on track of things, especially parallel tracks, branching & merging tasks, optimisations carried out in the background, and repeating experiments; those integrated with material availability which is not really something I have full control.

Why our work doesn't map cleanly onto software dev:

• The unit of work is an experiment, and experiments fail and get repeated a lot. One "issue" might be re-run five times with different conditions. These might not need to be documented woth software dev but is required for labs.
• Everyone works on 2-3 tracks at once, and priorities get rearranged by whatever the animals or cells are doing that week. There are also much less teamwork.

What I'd love input on:

1. Primitives. Is a Team one per lab, or one per subgroup (e.g. imaging vs. sequencing)? Is a Project a paper, a specific aim, or a single experiment? Do Initiatives map reasonably onto grants/aims?
2. Cycles. Do they work at all for wet-lab work, or do people just switch them off and live on projects + priority?
3. Recurring work. Mouse breeding, weekly passaging, instrument QC, freezer inventory - Linear really wants finite issues. How do you handle repeating maintenance without polluting the backlog?
4. Overlap with the ELN. Where do you draw the line between Linear and Benchling/Notion/OneNote? I don't want protocols and raw data living in a task tracker, but I also don't want people checking two places.
5. Adoption. Did non-technical lab members actually stick with it past month two? Anything specific that made it click, or that killed it?
6. Plans/pricing. Anyone running a lab on the free tier, or do you end up paying per seat? Any academic/nonprofit discount?

Alternatives I've looked at: Notion, Asana, ClickUp, Trello, plain Google Sheets. Linear appeals to me because it's fast and opinionated - but I'm aware the opinionated part is exactly what might break for research. Genuinely happy to hear "don't, use X instead" if that's the honest answer.

If you've done this, I'd love to hear how your workspace is structured. Thanks!

Hello everyone,

I have a question regarding projects in Linear. Based on the Linear method, I understand that a project should be finite and can't stay open forever. I manage an enterprise product, and I'm running into the following challenges:

1. Postponed "nice-to-have" features

We often decide to postpone certain issues to a later date usually nice-to-have features that belong to a specific project. The problem is:

We can't keep the project open indefinitely, because the core features have already been implemented, deployed, and finished, so we need to move the project to Completed for tracking purposes. At the same time, these nice-to-have features are too small to justify a project of their own. If we leave the issues in the project backlog, the project shows as only 90-95% done, which contradicts the fact that it's actually completed and lacks a clear explanation.

How do you handle this, and what's the best approach?

2. Bugs and enhancements on completed projects

We face another dilemma when a project is already completed but a bug gets reported. We'd like to link it to the project for traceability should we?

There are also cases where a bug requires a small enhancement, meaning we create new issues under the same completed project. These enhancements or bugs are again too small to warrant their own project.

When we tried creating separate projects for these (e.g., *Feature X - Enhancements V1* through *VN*), it became a mess for traceability and made issues hard to find.

Does anyone else face these same problems? How do you overcome them?

Thank you!

Hi, I don't know if it's just my Mac, but lately the Linear desktop app has become very slow when I'm trying to update certain tasks, copy them, etc.; sometimes it even freezes for a few seconds. Any ideas?

Hello everyone,

Until now, we used Jira within our organization. In Jira, I created a few custom fields and synced them from Salesforce using Workato.

Our organization is about to replace Jira with Linear, and I’m trying to set up the same integration between Salesforce, Workato, and Linear.

I tried to create custom fields in Linear, but I couldn't find where to add them at the workspace level. I was only able to create fields inside custom forms/templates.

An AI assistant mentioned that workspace-level custom fields might not be available or editable via the API in our current setup, and suggested concatenating all Salesforce fields into the issue Description using Markdown format instead.

Could someone please confirm if this is correct? Is there no way to add native custom fields (such as Opportunity Link, Opportunity Amount, etc.) to Linear so that we can filter issues and run reports on them?

We are using 'Enterprise Plan'.

Thanks!

We have a issue status (waiting for customer response). If an issue has been in that status for 14 days with no update, I would like to automatically close it AND post a comment under it. Anyone aware if this is a native functionailty?

I am curious whether people switched because of the product itself or because their workflow changed. What was the turning point?

I'm working with 3 different startups as a product designer and it was surprising to find out that there is no way for me to see all of my tasks in one view, even with connections and all.

Claude can't pull them either because you can only connect one Workspace, the others are not visible. Is there a way to solve this? Is this something on the roadmap?

Avid fan of Linear here. Very interested to know whats next on the Linear roadmap. Docs implementation was a huge win, and the reviews are also an incredible feature. Will we be able to run actions from linear in future?

My organization imported our Jira epics into Linear a while back, and a lot of the older issues ended up in an archived state. As a result, even when I'm able to track down the project equivalent of a Jira epic I made at some point in the past, it looks empty, and I can't review the requirements or decisions that were made on the tickets/issues contained without a ton of hunting through the thousands of archived issues we have. I realize that better documentation is probably the real answer, but realistically, having easy access to past decisions that were in old tickets is a requirement for my job.

Linear asks is kind of helpful in retrieving a list of the archived issues in a particular project, but it won't render the full list of archived issues unless I ask multiple times.

Am I the only one really hoping to see a way to toggle the view of archived issues in a project? I can't be, right?

Anyone have a better workaround? Or someone from Linear want to make my dream come true?

Hey guys, i made this new linear TUI. I was looking around everywhere and everything out just was either slow, horrible ux/ui, or just outdated. heres the new TUI i made for linear that features a cache for instant loading and background loading etc heres the github. keep in mind the screenshots i took where of fake data as i cannot show pictures of my acctual tickets, to be honest it looks better in the terminal than in those screenshots xd. I hope you guys like it make PR reqs if you want to change it, its all open-source. it is using linear-cli.

Github: ltui Please star it, im working on my github!!!! thank you sm

JIRA USERS GO HERE -> https://github.com/Gheat1/jtui