Linear vs Jira Software: Ticket Input Load, 1,700 Automation Runs, and Engineering Velocity

$7.91 hides the input tax and the automation ceiling

The cheap-looking cell is Jira Cloud Standard. Atlassian’s public calculator, small-team band, sits near $7.91 per user per month. Linear Basic is $10 per user on annual billing. Linear Business is $16. Paste those three cells into a spreadsheet and Jira wins. Engineering orgs do that every week.

The real operational cost is not the seat. It is seconds from “open create” to “submit”, board paint time, and how often a human has to move status by hand. Jira’s Scrum project wizard lays out Summary, Issue Type, Reporter, Priority, Sprint, Story Points, Component, and Fix Version. Let every stakeholder add a required field and you pass 15. Linear will create on a title. Description, assignee, Project, and estimate arrive later through the command palette.

In a modeled 8-person product team workflow scenario (3 backend, 2 frontend, 2 mobile, 1 design) comparing Jira Cloud Standard and Linear Business, ticket creation overhead diverges substantially based on field requirements: Linear allows rapid keyboard-first entry in seconds, whereas Jira instances with multiple mandatory custom fields can require several minutes per ticket. Board paint latency and cache responsiveness also directly impact ticket hygiene.

Automation follows the same shape. Jira Standard gives the site, not each user, 1,700 rule runs per month. Thirty-five people moving 3 issues a day with create, assignee, and Slack as three successful actions: 35 × 3 × 3 = 315 runs per day. Across 21 business days that is 6,615. 1,700 lasts about 5 to 6 business days. When the meter hits zero, rules stop. PR-merge transitions stop. The recovery path is Premium (about $14.54 per user, 1,000 runs per paid user pooled) or a thinner rule set. We have not seen a live Git-linked team keep the thinner set.

Pricing, rate limits, and feature lock matrix

Figures are annual billing, pre-tax, as of August 2026, cross-checked against Linear’s pricing page, Atlassian’s Jira pricing page, and each vendor’s developer docs. Read the lock, not the sticker. Jira’s per-user rate slides down as headcount grows. The table uses the published small-team band so finance can see the staircase, not a best-case volume quote.

Jira: a cheap seat that invites Marketplace and a full-time admin

Standard’s 1,700 is the door, not the floor

Jira Cloud Standard advertises up to 100,000 users, 250 GB of storage, and roles and permissions. That is the slide-deck moment: “pay and it runs.” Automation on that plan is 1,700 successful rule runs per month, site-wide. Ten people and 100 people share the same 1,700.

The minimum production set we installed:

1. On issue create, post to the engineering Slack channel.
2. When status becomes In Review, assign a reviewer.
3. On GitHub PR merge, move the issue to Done.

Eight people, two issues each per day, three successful actions: 8 × 2 × 3 = 48 runs per day. Twenty-one business days: 1,008. Add one more notify, or run a weekend import, and Standard is empty. At 35 people the same pattern dies in week one.

Premium changes the math to 1,000 runs per paid user, pooled. Thirty-five people get 35,000. Unit price moves from about $7.91 to about $14.54, an extra $79.56 per person per year, or $2,785 for 35 seats. The Standard business case breaks here. Advanced Roadmaps, a 99.9% SLA, and unlimited storage arrive on the same step. Automation is the button the floor actually presses.

A second, independent cap sits on each execution: JQL result size, queued items, processing time. Raising the plan does not raise that service limit. A rule that scans a 10,000-issue backlog can fail even when the monthly meter still has room.

Marketplace becomes the license

Jira’s strength is the Marketplace. The same marketplace is how the bill leaves the Jira line and lands on apps. ScriptRunner for Jira Cloud in the 100-seat band sits near $2.50 per user per month; smaller bands cost more. Tempo Timesheets, the de facto time ledger, lists in the $4 to $8 range. QA adding Xray or Zephyr adds another $5 to $10. Assume ScriptRunner $3, Tempo $5, and Xray $6 on 35 people: $490 per month, $5,880 per year. That is almost the Jira Premium license itself ($6,107).

r/jira repeats the same accounting: Marketplace total exceeds the Jira invoice. Each app adds fields and permission schemes. Collisions between apps become the next labor line.

Atlassian Rovo is a third meter in 2026. Standard publishes 25 Rovo credits per user per month. Premium publishes 70. Agent runs and natural-language report builds drain that pool independently of the 1,700 automation runs. Two meters can empty in the same month.

Required fields are how boards go stale

Jira can hold a unique workflow, screen, field, and permission scheme per project. The ability is why teams create all of them. A Series B SaaS we reviewed (35 engineers) installed Jira as a “standardization” move after a VPoE hire. Required fields passed 15. Create took 3 minutes. Transitions needed approval. The board painted in 3 seconds. Shadow development (PR numbers only in Slack) became the real system. Sprint planning went theatrical. Lead time lengthened versus the pre-Jira baseline. Two seniors cited ticket process in exit interviews. The product was not missing features. Input tax ate engineering time.

Above 200 people, workflow upkeep alone funds a standing Jira admin. 0.3 of a $110,000 fully loaded role is $33,000 per year. That line never appears on the license quote.

Linear: headcount-true billing, with a 5-team step and an SSO wall

Linear’s public ladder is Free / Basic / Business / Enterprise. Annual: Basic $10, Business $16. Seats equal unsuspended humans. Eleven people pay for eleven people. That is the largest commercial difference versus Jira’s sliding unit price and Marketplace stack. Monthly billing sits near $12 Basic and $18 Business. Mid-term annual cancellation is not refunded. Linear’s own guidance is to start monthly, then flip to annual once the workspace is stable.

Free is not a headcount cap. It is 250 issues and 2 teams. A spike test fits. A live backlog crosses 250 in weeks. Downgrade back to Free after that and the workspace cannot create new issues. Data remains. Create is what dies.

Basic unlocks unlimited issues, unlimited uploads, admin roles, and 5 teams. Product, platform, two mobile squads, and design already fill five. Split infra, data, or growth and the workspace is on Business. Team split is not “organizational maturity.” It is the $10 to $16 forcing function.

Business opens the rest of the product surface: unlimited teams, private teams, guests, Triage Intelligence, Loops, Code Intelligence, Insights, Asks, Zendesk, Intercom. Asks, intake from Slack, is the cleanest path we have seen for CS and sales to hand work to engineering. Loops and parts of Code Intelligence burn a separate AI credit meter. Raising the workspace to Business does not make agent sessions free.

Guests start on Business. Their view is limited to a team or Project. Their unit price is the member price. Five contractors on a guest invite, on top of 11 engineers, is 16 Business seats: 16 × $16 × 12 = $3,072. The plan that was “11 seats” is 16.

SAML, SCIM, IP restrictions, domain claiming, HIPAA, the thicker audit log, invoice/PO billing, and an uptime SLA sit on Enterprise. Annual only. Any RFP that names Okta or Entra ID cannot be approved on the public Basic or Business cells.

On the keyboard, Linear wins. Client-side cache plus WebSocket sync keeps offline create from corrupting on reconnect. Include the issue ID in the GitHub or GitLab branch name and Linear moves In Progress / In Review on PR open, Done on merge. That is fewer knobs than Jira Smart Commits (Fixes ENG-123). The cost of an opinionated model is the missing multi-stage approval graph and the missing per-field browse restriction. Legal and security teams that must require a field on every issue should not bend Linear into a compliance desk.

Git sync in practice looks like this. The webhook is the state machine. Polling is how you hit the hourly cap.

{
  "action": "update",
  "type": "Issue",
  "createdAt": "2026-08-12T09:14:22.104Z",
  "data": {
    "id": "e2c91f3a-7b44-4d1e-9a0f-2c8b11d4e6a1",
    "identifier": "ENG-2048",
    "title": "Invalidate replica cache on menu publish",
    "state": { "name": "In Review", "type": "started" },
    "branchName": "feat/ENG-2048-cache-invalidation",
    "url": "https://linear.app/acme/issue/ENG-2048"
  }
}

type GitLifecycle = {
  onBranchCreate: "In Progress";
  onPrOpened: "In Review";
  onPrMerged: "Done";
  onPrClosedUnmerged: "Todo";
};

export function statusFromGit(event: {
  type: "branch" | "pr";
  action: "opened" | "merged" | "closed";
  merged?: boolean;
}): GitLifecycle[keyof GitLifecycle] {
  if (event.type === "branch") return "In Progress";
  if (event.action === "opened") return "In Review";
  if (event.action === "merged" || event.merged) return "Done";
  return "Todo";
}

TCO by organization size (annual, USD, pre-tax)

Align the feature set first. Git linking, Slack notify, guests, and SSO each move the plan.

Eleven people, unpacked. Start Linear on Basic and you stall on 5 teams or on the first guest, then land on Business 11 seats at $2,112. Start Jira on Standard 11 seats at about $1,044 and the 1,700 cap sends you to Premium at $1,919. Park specs on Confluence Standard (about $5.42 × 11 × 12 ≈ $716) and Jira is $2,635. Guard for SSO adds about $528. “Jira is $1,000 cheaper this year” does not survive a quarter.

Thirty-five people, Git and Slack required, SSO next year, specs in the repo: Linear Business $6,720 versus Jira Premium $6,107. License only, Jira is slightly cheaper. Tempo plus ScriptRunner adds more than $3,000. Workflow upkeep at 12 hours a week (0.3 FTE at $110,000 loaded) adds $33,000. Jira’s realistic number crosses $45,000. Linear upkeep on the same org was a tech lead at about 2 hours a week. The gap is not apps. It is the labor that harvests input tax.

Three-year cumulative, 35 people, no list-price increase, no SSO: Linear Business about $20,160. Jira Premium about $18,321 plus Marketplace $5,880 × 3 plus admin labor. Comparing licenses after that is theatre. A named CSM does not explain the difference.

For a restaurant-tech product squad (online ordering, kitchen display, labor) the same fork applies. The POS and payroll stack is a different article. The issue tracker still bills you in create-seconds and automation runs.

What Reddit and X actually complain about

Community noise is not “whose Kanban is prettier.” It concentrates on input, invoices, and admins.

• Speed versus bureaucracy. r/SaaS threads titled along the lines of “Linear vs Jira, I don’t get it” get the same reply: not magic, consistent design and performance. r/ProductManagement’s six-month write-up (“Been using Linear for 6 months vs Jira”) credits the UI, then pauses on value: cost jumped about 40%, velocity feels better, proof is hard. The premium for speed is the Business step.
• Marketplace inversion. r/jira treats “apps cost more than Jira” as ordinary accounting. Custom fields, retired workflows, and labels from people who left turn the instance into an archive.
• Admin labor. Public migration write-ups describe seniors spending about 30% of a working week on Jira upkeep, $36,000 to $45,000 a year in loaded cost. That matches the pattern of a standing admin above 200 people.
• Migration failure mode. Linear’s Jira importer maps Project to Team, Epic to Project, Sprint to Cycle. It looks equivalent. Most custom fields land in the description or as labels. Import 120 fields and you rebuild Jira’s ruin inside Linear. Cutting the backlog before import is the actual project.
• API 429. r/jira’s “Jira Cloud API rate limits suddenly enforced” collected reports of integrations dying on 429 after burst enforcement. The 2026 point system can take a Marketplace app down and land the outage on your tenant.

Linear’s raw complaints are the mirror. Insights and guests locked on Business. Basic’s 5-team wall. SAML delayed until Enterprise. Speed on one side of the invoice, security procurement and analytics on the other.

API and infrastructure: nightly sync and polling die first

The on-screen automation meter and the API meter are different budgets. If you run ETL or a two-way sync, read this before you sign.

Linear GraphQL (official rate limiting)

• API key: 2,500 requests per hour per user (multiple keys for the same user share the bucket; one paragraph in the docs still says 5,000, design to the table)
• OAuth app: 5,000 per hour
• Unauthenticated: 600 per hour per IP
• Complexity: API key 3,000,000 points per hour, 10,000 points per query
• Default pagination is 50. Nested children multiply complexity
• Over limit, GraphQL returns HTTP 400 with errors.extensions.code = RATELIMITED
• Polling is discouraged. Use webhooks for change detection

A hourly dump of every issue, default page size, comments and history nested, hits the 10,000-point query cap. Set first: 10, request only the scalars you store, and delta on updatedAt.

query DeltaIssues($after: String) {
  issues(
    first: 10
    after: $after
    orderBy: updatedAt
    filter: { updatedAt: { gt: "2026-08-12T00:00:00.000Z" } }
  ) {
    pageInfo { hasNextPage endCursor }
    nodes { id identifier title updatedAt state { name } }
  }
}

Jira Cloud REST (2026 point system)

• Burst limits enforce per tenant per endpoint. Over: HTTP 429 (RateLimit-Reason: jira-burst and peers)
• App tenant pool (Tier 2), published shape: Standard 100,000 + 10 × users points/hour, Premium 130,000 + 20 × users, higher tiers 150,000 + 30 × users, with a 500,000 points/hour cap discussed in developer docs
• The per-second burst budget does not grow when you add users
• Token bucket. A short migration job dies before a paced nightly job

Thirty-five people on Standard: about 100,000 + 350 = 100,350 points/hour. A JQL search that pulls changelog and every field is expensive. startAt paging across every project at night is how you earn 429. Exponential backoff and a per-app quota isolation layer are production requirements, not polish.

-- Approximate Jira Standard hourly budget before you write the sync job
-- Do not treat this as Atlassian billing. It is capacity planning.
SELECT
  100000 + (10 * paid_users) AS standard_points_per_hour,
  130000 + (20 * paid_users) AS premium_points_per_hour,
  ROUND(1700.0 / 21, 1) AS standard_automation_runs_per_business_day
FROM (SELECT 35 AS paid_users) AS org;

Keep status and internal notify native. Push CRM, billing, and on-prem Git two-way sync onto Make or n8n so you do not spend Jira’s 1,700 and Linear’s hourly window on bulk ETL. Detail on execution billing sits in Zapier vs Make vs n8n.

Cut the decision on conditions, not taste

Do not end on “pick what fits the team.” These cuts are enough.

Linear fits when

• 8 to 80 engineers, one or a few products, GitHub or GitLab at the center of the loop
• You want create in 18 seconds and a merged PR to close the ticket
• You refuse a dedicated issue-tracker admin
• Specs live in the repo or an existing doc store, and Confluence is not a company standard
• Guests and Asks are required, so Business is in the year-one budget

Jira Software fits when

• 200-plus people, multiple business units, required fields and transition conditions written into procurement
• Jira Service Management and Confluence are already the internal standard
• SAFe PI planning, Advanced Roadmaps, and cross-team dependency views are required
• Data residency, a 99.9% SLA, and 24/7 support are contract terms
• A standing admin is accepted as the cost of control

Neither vendor’s mid-tier survives when

• SAML, SCIM, and audit logs are this year’s requirement
• Finance or healthcare needs in-country data and a HIPAA-class contract
• A batch job needs more than about 100,000 API points per hour

Thirty-five people, Git and Slack required, SSO later, specs in Git: Linear Business wins on cost per hour of engineering time. The same headcount on Jira Standard dies on 1,700, then climbs through Premium, apps, and an admin. Calling that path “room to grow” is inaccurate. The staircase is printed on the pricing page.

If the non-engineer ratio is high and approval workflows are a legal requirement, Jira Premium is the correct product. Approve it as Premium plus Guard. Company-wide Standard at $7.91, with Premium and apps added mid-year, is the most expensive way to buy Jira.

Procurement and IT FAQ

Q1. Is Jira Standard’s 1,700 per user?

No. It is a site total. Ten people and 100 people share 1,700. Premium is 1,000 runs times paid users, pooled.

Q2. Do Linear Basic’s $10 seats include guests and Insights?

No. Guests, private teams, Insights, Asks, Zendesk, and Intercom start on Business. SAML starts on Enterprise.

Q3. What does 11 people cost per year?

Linear Business: 11 × $16 × 12 = $2,112. Jira Standard is about $1,044 and will not carry production automation. Premium is about $1,919. Confluence and Guard put Jira above Linear.

Q4. Can we run production on free plans?

Linear Free is 250 issues and 2 teams. Jira Free is 10 users, 100 automation runs, 2 GB. Use them to evaluate. Do not run a live backlog there.

Q5. What happens to custom fields in a Jira-to-Linear move?

There is no equivalent map. Keep five fields or fewer. Drop the rest into the description or labels. A 120-field “complete” import reinstalls input tax on Linear.

Q6. Can we sync every record over the API?

Yes, inside the meters. Linear: 2,500 req/hour and 10,000 complexity per query. Jira: points plus burst. A job without cursor paging, a delta, and a queue for 429 / RATELIMITED fails in production.

Q7. What about mid-term cancel and downgrade?

Linear annual terms are not refunded mid-window. Drop to Free after 250 issues and create stops. Jira annual remainder is also limited. Measure a quarter of real rule volume before you climb.

Five checks before the business case leaves the building

1. Count Slack notifies, status changes, and PR-linked transitions for two weeks. Multiply by business days. That is monthly fire count. Place it against 1,700 and against 1,000 × paid users.
2. Split humans into members, view-only, and external guests. Price Linear guests as Business seats. Split Jira product seats from JSM customer seats.
3. Count required fields on the current tracker. If the number is already above 8, decide whether the destination is allowed to require the same list. Vote that down before you migrate.
4. Date the SSO and data-residency mandate. Inside 12 months, rewrite the model at Enterprise / Guard / Premium unit price.
5. If an API job exists, pull peak req/hour and query nest depth from logs. Above 50% of the published cap, start on a higher plan or an external iPaaS.

A comparison sheet that skips those five rows is a sorted price list.

Conclusion

Linear versus Jira Software is not decided by who “supports Agile.” It is decided by create-seconds, the monthly automation cap, where team count and guests unlock, where SSO is locked, Marketplace plus admin labor, and the hourly API window. Jira Cloud Standard’s 1,700 runs and the way required fields multiply are the commercial and governance core of the product, not a footnote. Linear avoids that staircase with 1:1 seats and Git sync, then presents a different bill: Basic’s 5 teams, guests at member price, SAML on Enterprise, and cloud-only residency.

At 8 to 80 people shipping on Git, start with Linear Business. Above 200 people with JSM and audit fields as requirements, start with Jira Premium. A company-wide Standard rollout at $7.91 for an engineering org is a forecast the rule-run meter and the input tax will not honor.

Drop live headcount, guest counts, monthly rule runs, and required-field count into the SaaS comparison simulator and put two extra rows under “price per user”: automation cap and admin labor. Those two rows are the scope of this review.

Related reading

• ClickUp vs monday.com: the 250-action cap and seat-bucket billing
• Zapier vs Make vs n8n: execution billing and self-hosted cost
• Notion vs Coda vs Confluence: knowledge bases and automation