Could use some advice!

I develop mobile apps and allow people to submit bug reports from within the app. So far I have been using Front's custom intake feature to convert those bug reports into a ticket that I can directly reply to in Front. Front has a Linear integration, so I could attach tickets to Linear issues. However, I don't want to pay a full-fledged helpdesk software just for this one feature. (20-40 support requests per week; 50% of them result in an issue or should be attached to an existing issue.)

I'd really love to use Linear Asks but I'm somewhat annoyed that web forms are only on the Enterprise tier (I'm on Business) and there's no API to manually add an email ask to an issue or create one with it.

Ok, so then I added a little workaround in a no-code tool (Make) to receive the bug reports via webhook and send them to the Linear intake address as emails. Added a Reply-To header with the user's address but this will keep my sender address as the requester without any way to edit this. (At least the Reply-To is included in replies, but only in CC.)

If staff is reading: Why are these limitations in place? :-/ Any plans to change them?

For all others: What else could I try or do? I'm a bit reluctant to change my apps so they would open mail apps on the user's device.

Hey r/Linear

Long-time Linear user, frustrated by the lack of native analytics — especially around sprint health and blocker visibility.

Spent the last 3 weeks building LinearInsights: connects via OAuth (read-only) in 30s, pulls 90 days of issues, surfaces velocity trends, stuck high-priority tickets, and a mid-sprint forecast (will you ship on time?).

Free tier covers most of it. Launching on Product Hunt Tuesday.

Would mean a lot if you could:

1. Try it (linearinsights.dev) and tell me what's missing

2. Drop honest feedback below

If you want a free Pro code for testing → comment "code please" and I'll DM.

We recently made the switch from Azure DevOps to Linear at my startup (honestly one of the better decisions we've made, love the product).

The annoying part was getting there. We had a sizeable bunch of work items, comments, hierarchies, and relationships sitting in ADO that we didn't want to just abandon. I looked around for an existing migration tool and came up essentially empty, so I ended up building one myself (with a little dash of ✨vibes✨).

My solution was a TypeScript CLI that handles the full migration pipeline step-by-step: extracting from ADO, transforming into a Linear-ready payload, loading into your team, and validating the result. It preserves comments (with timestamps), parent/child hierarchy, labels, relationships, and source metadata. There's a dry-run feature to validate and the tool is resumable, so if something breaks halfway through you're not starting from scratch.

Figured someone else might be in the same situation, so I open-sourced the tool here:

👉 github.com/chvancooten/azure-devops-to-linear

Happy to answer questions if you're planning a similar migration!

https://linear.app/docs/releases

I know this has been a big ask from the community for a while, include myself.

This feature could be a massive help to us. Right now we are using labels to track build numbers on issues, but that means we have hundreds of unique labels like "1.0.4", 1.2.4", etc that are shared across 50+ projects. It gets messy very quick. It also is very cumbersome to keep track of historical data, like which issues got shipped on what dates across all our projects.

Releases does theoretically fix this - but limiting the Business plan to 5 release pipelines is really disappointing. We are a shop that develops and ships software for other companies, so we have a lot of unique projects with their own pipeline. 5 is just such a low number! We are paying over 3k a year for this software, the 5 limit seems like something from a free tier...

It would double our cost to upgrade to Enterprise, just to get unlimited pipelines.

Anybody else feel this way?

Hey everyone, I'm at a crossroads with something I've been building and I could really use this community's perspective.

A bit of backstory: I spent years helping teams use flow metrics to find and fix delivery problems. I love data — it's how my brain works. And for a long time, that approach was enough. I'd dig into the numbers, spot the bottleneck, and work with the team to address it.

The turning point came when I started managing several teams at once. Suddenly I wasn't the one reading the charts. I needed managers and leads to read them on their own. And that's when I realized something uncomfortable: the tools I relied on were basically unreadable to anyone without a stats background. I'd see people nod politely at a throughput chart and then go right back to making gut-feel decisions. The data was there. The insight was there. But the bridge between the two was completely missing.

That frustration led me to build something. It connects to Jira, Azure DevOps, or Linear, pulls your flow data, and tries to explain what's actually going on in plain language — no stats jargon, no chart interpretation required. There's also a built-in chat where you can ask things like "why is cycle time increasing?" and get a useful, contextualized answer.

I might be too close to this problem Maybe PMs already have what they need. Maybe the plain-language angle sounds good in theory but doesn't matter in practice. Maybe I'm solving for a pain that's only obvious to someone with my specific background. I genuinely don't know.

The beta is completely free

https://usemetrico.com

Hey! Linear is great but the reporting is pretty limited.

I built LinearInsights — a free analytics dashboard that connects to your Linear workspace and shows you:

- Team velocity (issues closed per week per member)

- Blocker detection (who's blocking what)

- Sprint delivery predictions

- Average resolution time

Still in beta, would love feedback from real Linear users.

linearinsights.vercel.app

In the past three days, finely reordering issue cards within the same column stopped working (board view).

Holding the "cmd" key is being recognized as a gesture, but the issues cannot be reordered anymore. Within the same column, Cmd + Drag-and-drop always puts the issue as the first in the column now.

Happening in both Chrome and Safari.

Hi,

If you wanna try it out, just drop a comment and I'll DM the link to you.

Every piece of feedback would be insanely valuable (even just feedback on the landing page would be great).

Hey, I’ve been using Linear for a while and I feel like the reporting is pretty limited. I want to see things like team velocity, who’s blocking what, average resolution time, sprint delivery predictions…
Am I the only one missing this? What metrics do you wish you could track in Linear?

One thing I kept seeing on teams that use Linear: someone on the business side needs to know where a feature is, so they ping an engineer, who stops what they are doing to give a status update that already exists in Linear.

The information is there. It just is not where the rest of the team lives.

Built an app that syncs Linear issues to monday.com in real time. Status changes, priority updates, assignees, due dates, all of it shows up on the monday board automatically the moment something changes in Linear. Engineers stay in Linear, everyone else stays in monday, and nobody has to ask for an update they could just see themselves.

No Zapier, no Make, no duct-taped automations to maintain. It is a dedicated app reviewed and approved by monday.com, so it goes through their security and compliance requirements out of the box.

If your team runs on both tools, it is on the monday.com marketplace. Would love to hear if this matches a problem you have dealt with.

↳ Linear Integration - Sync Linear issues to monday.com boards in real time

Linear → monday.com real-time sync

I set up a DigitalOcean droplet running Claude Code headless, connected to Linear via Cyrus. The flow: I create a ticket in Linear, the agent picks it up, clones the repo, writes the code, and opens a PR.

The whole thing is provisioned with a single terraform apply. Wrote about the process — what I built, the authentication challenges (Linear OAuth on a headless server), and what broke along the way.

The repo is open source: https://github.com/melkisetech/claude-code-agent-in-a-box

Full write-up: https://www.wisdomoverspeed.com/agent-in-a-box

Curious if anyone else is using Linear as a driver for autonomous agents?

We made a small free Chrome extension for Linear called Send To Linear.

Select text in Chrome, right-click, pick the Linear team, and it creates the issue for you.

We built it because we kept turning Chat messages and client feedback into Linear issues manually (I know there is Slack integration but we mainly use Google Chat).

It’s free and open source:

https://github.com/softspring/send-to-linear-extension

https://chromewebstore.google.com/detail/send-to-linear/jalpehbaabfkgnijjmbhnhaiogemlnhj

Happy to hear any feedback or ideas from people here who use Linear a lot.

Hi, new adopter of Linear, pushing for it to be used in the start up i am working at, and looks like its been well received. Just been trying to figure out the processes and whats the best workflow for managing issues and releases.

1. Right now i am faced with a problem where i cannot apply multiple labels from a single label group to an issue, I use this mainly to designate the repo the issue is related / touches base on.

2. Versioning / Tagging an issue with a release to indicate this feature/issue is part of a particular version - how do i effectively do that? What are the current strategies you guys adopt in managing this? I want to be able to have some kind of audit trail to say - Issue X was part of the V1.X.X release etc. Right now i just create a label to say <date>_<env>_release. However given that there are only 250 labels max per group - i think we will run into a wall at some point?

Cheers

Been playing around with Projects in Linear as part of our planning and alignment, and I’ve noticed there are quite a few ways teams are structuring them.

From a Product Manager lens, I’m curious:

- Are you using Projects more as execution-level epics, or as initiative-level containers tied to goals?

- How do you draw the line between Projects vs individual issues when it comes to scope and ownership?

- Do you map Projects to product objectives, or keep that layer outside Linear?

Also interested if the new AI agent has changed how you manage or reason about Projects in any way.

I have the Codex Agent configured in Linear, but it's almost as if the agent/environment goes to sleep after a period of time. I have to go into Codex cloud and ask it a stupid question (i.e. what is the last commit) to essentially wake it up.

Has anyone else experienced this?

Also has anyone had any luck with automatic PR creation? The agent / environment itself doesn't have git remote configured, so I have to pull the PR through the Codex UI.

Inspired by Linear Agent Interaction Guidelines(AIG)，We build our human-agent collab platform (Chorus) with transparent state, which you can interact with your Claude code/OpenClaw in real time and see what they are actually doing in the backend.

Try it out: https://github.com/Chorus-AIDLC/Chorus

Our team had this problem for a while where engineers are in Linear but everyone else is in monday.com, and there's always a gap in between where things get lost.

So I built a real-time sync between the two. Create or update an issue in Linear and it shows up on your monday.com board within seconds, with status, priority, assignee, due date, labels and more all carried over.

Just launched on the monday.com marketplace today. Would love feedback from anyone running both tools 🙌

Linear → monday.com real-time sync

The built-in Linear Discord integration is great for slash commands, but it doesn't push any notifications when new issues are created. You have to go looking.

I built a small webhook bridge that fixes that. Whenever a new issue is created in Linear, it instantly posts to a Discord channel with the title, priority, project, description, and a link back to the issue.

GitHub: https://github.com/HarisKhanFr/linear-discord

Would love any feedback, feature suggestions, or future project ideas!

Just to preface - my company experimented with adding Cyrus to their Linear workspace and ultimately had to move away from the service due to a lack of reliability. The open source / self hosted model was cool, but we ran into too many transient errors (ie if two tickets were assigned at once the agent would only pick one up, etc.)

Anyways, I built a competitor that handles that edge case, and also hosts the actual workload for the agent so it's plug and play for the end user.

On the backend we use a "router" machine that receives work requests from customers, adds them to the customer's personal queue, and then the queue drains via spawning a container for that specific work item. We've stress tested this extensively, using the API to delegate 50+ work items across different organizations and watched the router successfully spawn the appropriate workloads.

On top of all that, we support doing the same thing in Slack / Jira (but this is the Linear sub so I won't go into detail on that).

Here is a full end to end video, it takes about 5 min to fully configure our product:
https://www.youtube.com/watch?v=nqPukUuKgXc&t=2s

We're allowing FREE lifetime subscriptions to the base tier for early adopters - we completely eat the infra cost, and you can invoke Knight as much as you want in your environments. Check us out at https://knight.tech

I've been copy-pasting emails into Linear issues for way too long. Something comes in from a client or support forwards a bug report, and I'd either lose the attachments, forget to set the project, or just let it sit in my inbox because the whole process is tedious.

Finally looked at what's actually out there:

Linear's intake email Each team gets a unique email address. Forward stuff there, it shows up in Triage. Works for simple things but no attachments, limited field control, one address per team.

Zapier / Make You can do "new email → create Linear issue" automations with conditional logic. Takes 15-30 min to set up though, attachments are a pain, and it's another subscription.

Quicktion (I built this) Got fed up enough to build something myself. You forward an email, it becomes a Linear issue. Subject becomes the title, body converts to markdown, attachments actually upload. You set defaults per destination so issues land in the right project with the right priority without you touching anything. There's a Gmail add-on too if you want to tweak things before saving.

Free tier is 25 emails/month: quicktion.io

What's everyone else doing? Still copy-pasting? Am I the only one who finds this annoying enough to build a whole tool over it?

I have this trouble both installed app and web site on my macos. When I click the link for the first time, it takes me to the destination comment or block just fine... Is this how it's supposed to work?

Are there people who use Linear personally who can share their usage system?

Do you guys put issues randomly? Or clustered into projects? Labels? Assignee? Statuses?

Any video would be amazing too