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, losing metadata and workflow flexibility
.76
Demand — how loud & how many (score)
Willing to payImplicit
Momentum (7d)▼ 1.5%
Cluster17 posts · 16 people
MarketplaceLinear Integrations
Updated18d ago
The story
The pain
We moved from Jira to Linear and had to drop a ton of metadata because there are no custom fields. Putting that data in the description is unstructured and error-prone, especially when AI agents mess up the copy/paste. We need to work our own way, not how Linear tells us, and the lack of custom fields is a major blocker for automation and agentic workflows.
Evidence
What people said · 17 complaints, 16 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.
It seems that Linear doesn't have custom fields [like Asana](https://asana.com/guide/help/premium/custom-fields), but on import from Asana it could at least: - Offer the option of using labels to replace label-like (dropdown) custom fields - Append other custom fields and values as text within the issue description, so that they are visible and searchable in an unstructured way, even if not cleanly filterable.
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.