DevOps / SRE / Platform · 12.08.2026, 22:25 UTC
“Issue tracking is dead”; How the pull request became the last chokepoint in the SDLC bottleneck
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | The New Stack ↗ |
| Veröffentlicht | 12.08.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
AI code review specialist CodeRabbit announced its Agentic Change Management control layer on Wednesday. The service is intended to help software engineering teams understand, govern, and ship software created by human developers and agents alike.
The company has suggested that issue tracking systems (such as Atlassian’s Jira, GitHub Issues, or Linear) were built for a simpler time. Back in the good old days, product managers and engineering leaders had time to do team capacity planning and curate a backlog of ideas, support requests, and requirements before assigning work to developers.
CodeRabbit CEO, Harjot Gill, tells The New Stack that today, AI has driven a new world order in software engineering where the conventions and mechanics of the Software Development Lifecycle (SDLC) no longer hold true.
Issue tracking is dead
“Issue tracking is dead and agents are building software faster than teams can align on what should be built,” Gill says. “That leaves the pull request as the last real chokepoint in the SDLC as the lifecycle itself now expands beyond reviews to plan, prioritize on what to ship, and decide which agent outputs to take to completion.”
As the marginal cost of producing code approaches zero, Gill underlines his statement and says that “the traditional SDLC now breaks down”, because it was built for a world where code was scarce and expensive – and that’s a constraint that no longer holds.
As we know, agentic platforms and tools can create code or open pull requests continuously; meaning that code increasingly exists before a team has established …