You're reading one of the top pains on Linear Integrations — a free sample of the catalog. Create a free account to browse all Shopify & Atlassian pains and the basic Chrome catalog.
Linear teams lack custom fields for structured metadata and automation
.91
Demand — how loud & how many (score)
Willing to payExplicit
Momentum (7d)▼ 1.7%
Cluster12 posts · 11 people
MarketplaceLinear Integrations
Updated19d ago
The story
The pain
We moved from Jira to Linear and immediately hit a wall: there are no custom fields. We used them for metadata, automation triggers, and agentic workflows. Now we have to stuff everything into the description, which is unstructured and breaks our AI agents. It feels like Linear is forcing us to work its way, not ours, and we're considering switching to ClickUp or back to Jira just to get this basic feature back.
Evidence
What people said · 12 complaints, 11 people
Lack of custom fields. We need to be able to work our way not how Linear tells us.
There are no custom fields in Linear by choice, frankly I wish they had it. I know it can get messy. But moving from Jira has been rough because we had to drop a bunch of metadata off the system. Putting it in the description is bad because it's unstructured and AI agents screw up the copy/paste a lot.
Linear is too busy building AI and Agents instead of building what we actually need like custom fields, guest or client views, or even more flexible pointing system. I really like Linear, been using it for over a year now, and sadly moving away to ClickUp for the sole purpose of inviting clients to our workspace to give them visibility, and found custom fields and automations, promising so far
Export the pain — problem, evidence and market signals — as Markdown, PDF or JSON. The Markdown export ships with a built-in briefing you can hand straight to a developer or an AI agent.