Jira and Linear are legacy software

TL;DR

AI agents are making traditional issue trackers obsolete because software development is shifting from ticket-based handoffs to context-driven, agent-executed workflows.

Key Points

• 1.Linear officially declared issue tracking dead. Linear published an article arguing the ticket-based handoff model — where PMs scope work and engineers execute it via queues — is obsolete, a bold move for the company that led that category.
• 2.Jira's complexity became its fatal flaw. At Twitch, the speaker's Jira dashboard took over 2 minutes to load due to excessive tickets, fields, and data links — a symptom of every feature being used and abused until the system broke.
• 3.Linear was built on the opposite philosophy from Jira. While Jira was marketed to PMs, Linear was designed to reduce overhead for engineers, winning far more startups despite Jira's scale advantage.
• 4.Agents are already transforming Linear's enterprise workspaces. Coding agents are installed in over 75% of Linear's enterprise workspaces, agent-completed work grew 5x in 3 months, and agents authored nearly 25% of new issues.
• 5.Linear's new vision replaces issues with context-driven execution. Their new model — feedback and intent become context, context becomes rules, rules command agents — eliminates sprints and issue lists entirely; new launches include a Linear Agent, Skills, and Automations.
• 6.The 'Theo prototype' method predates AI but predicts the future. The speaker's Twitch workflow of building a rough prototype in 1–3 days before writing specs — which half the time shipped as-is — mirrors what AI agents now enable at scale: code as planning, not documentation.
• 7.Jira's acquisition of the Browser Company signals it is falling further behind. While Linear rethinks the entire development workflow around agents, Atlassian/Jira is not engaging with these ideas at all, and its acquisition of the Browser Company is seen as a sign of misaligned priorities.