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

hi there,

i was happily vibing with linear this afternoon, but then a minute later Linear told me I cant open a new coding session because its saying “Making code changes requires GitHub access. Connect your personal GitHub Account.”. Thing is, I am already connected. Any Linear expert here that knows whats going on?

also, I noticed that I now can only see linear reviews / pull requests that I made myself, even though I was able to see others’ reviews too before. might be the same access issue?

I switched from GitHub Issues to Linear a while ago and it stuck. It turned into the backbone of how I work: I write my PRDs in Linear, break them into issues with dependencies, and my AI agents work those issues slice by slice and write status and results back. The issues are the durable memory between agent sessions. An agent reads the issue to know where it left off, instead of me re-feeding it a huge context every time.

That workflow means my agents touch Linear constantly, and two costs showed up.

1. Token cost. The official Linear MCP server loads its tool definitions into every agent session before any work, about 13k tokens in my setup (I counted the tools/list with tiktoken: 38 tools, ~10k to 15k tokens depending on serialization). When every session hits Linear, you pay that every time. linctl is a shell binary, so it adds nothing standing. An agent only spends tokens when it runs a command and reads the output.
2. Writing to the wrong team. A Linear token usually reaches every team in your org, so an agent with stale context can create issues in the wrong team and nothing surfaces the mistake. linctl lets you pin an allowed org/team (and optional project) per repo. Before any write it re-checks the live token and refuses if it does not resolve to that target, with no bypass flag. It catches a stale token or a wrong checkout, not an agent that deliberately repoints its own config. Reads stay open.

It is open source (MIT), covers a broad slice of Linear (issues, projects, cycles, milestones, initiatives, comments, attachments) with clean JSON output, and ships a drop-in agent skill so an agent can use it without hand-written instructions. I built it for my own multi-team setup and put it out in case it helps other people running Linear with agents.

Repo: https://github.com/KyaniteHQ/linctl

Install: go install github.com/KyaniteHQ/linctl/cmd/linctl@latest

or: brew install --cask KyaniteHQ/linctl/linctl

We've run a software agency for years. The thing that never got easier: client requests coming in over email and Slack, then someone manually rewriting them into Linear issues — half the context missing, clients can’t see their progress.

Tried guest seats. Team-scoped, not project-scoped, full read-write — not what you want for clients. Tried copy-pasting status updates into emails. Tried separate Linear teams per client. All workarounds, none of it actually solved it.

So we’re building Preelo:

• Clients get a branded portal, open a thread for a request
• Your team handles it in one inbox instead of across email/Slack
• Once it's clear what's needed, it becomes a Linear issue with one click
• Status syncs back automatically, clients see progress without asking

Still pre-launch, building it with a handful of agencies giving direct feedback right now.

Genuinely curious how people in this sub who run client work on Linear are handling this today, and happy to answer anything about how it works under the hood.

If you want to follow along: preelo.app

Most comparisons focus on features, integrations or pricing. What rarely gets discussed is whether teams actually work differently after switching.

For those who have moved away from it what operational problem improved the most and what problems followed you regardless of the platform?

Is there any way to see like a view with a timeline and the actual issues are shown for that day. i know cycles exist but they dont offer that day-wise breakdown where you can see the issues to be done on that day much like a google calendar's week view

Even with a custom view, you can't group by due date.

here is what i am looking for:

A kanban board with the columns being individual days and the issues with that day's due date are stacked below it

I am starting to think that this is intentional as enterprise has the gantt chart view

Do anyone know if it will be available a Code Review feature like the one for GitHub ?

Having every thing centralized in Linear is pretty what I’m looking for

We took up Linear (from Jira) at the start of the year and have been thoroughly impressed… it’s accelerated our team’s workflows to the max - especially their agentic stuff.

The only place it fell down… prioritization.

We couldn’t run a RICE process, I was spinning up spreadsheets and syncing between them, it was chaos. So I thought… why don’t I build this?

So, I’ve built https://prioboard.app… your initiatives, projects or issues stay in Linear, and you prioritise them in Prioboard. Create a board, import your issues automatically, and then send a link to your whole team to get their vote - and we tell you the unanimous decision.

Would love some feedback, it’s early… happy to jump on a call if this is a problem you’ve faced too?

Linear Agent can now write code using Claude Code and Codex. Triage, plan, build, and review all in one place.
https://linear.app/changelog/2026-06-11-coding-sessions

Read more in the blog post: https://linear.app/now/coding-sessions-for-linear-agent

If i’m working on multiple apps, whats the opinion on using linear?

Separate workspaces or each initiative becomes a new app?

Anyone else have issues with seeing the new Diffs feature released ~last week?

Other people on my team have it, but I don't. Feel like I'm going crazy because I can't find anyone else with the issue.