In 2025, automotive intelligence competition rages on. In this "software-defined vehicle" era, Jira—the Agile project management tool originally built for internet companies—has taken root in the automotive industry. But can Jira actually solve automotive R&D's complex processes? Why did it spread so fast, and why does it keep failing outside the smart cockpit?
Jira's Rise: Startup Legend to Industry Monopoly
Jira's dominance in Agile project management is overwhelming—it's almost synonymous with Agile. Recent financials show Atlassian grew revenue over 40% annually, with Jira holding 68% of the global Agile tool market (Forrester data).
Jira truly is a jack-of-all-trades in Agile scenarios. Many elegant product design details also inspired our own tool, MappingSpace.
When Jira Meets the Automotive V-Model: Compromises
When E/E systems and ADAS need ASPICE L2+/ISO 26262 compliance, Jira+Confluence faces a series of problems:
1. Dual Document Sources: Hidden Labor Cost
Jira's core is issue tracking, but automotive document management goes far beyond task lists.
Case: A company developing ADAS stores requirements, architecture, and detailed design docs in Word/Excel/PDF/Confluence. To establish traceability, these docs must be broken down into Jira Issues. When requirements change, teams update Jira Issues but forget Confluence docs—developers build based on outdated docs, causing 3 weeks of rework.
Pain point: Jira can't directly convert Word/Excel docs into itemized Issues—requires manual entry or custom Python scripts with ongoing maintenance, increasing labor costs 20%+.
2. Traceability Maze: Linking Can't Solve Coverage Statistics
ASPICE requires full-chain requirement-design-test traceability, which is hard to quantify in Jira. Many teams break docs into Jira Issues and create bidirectional links—but Jira lacks statistics on these links, so you can't see traceability completeness.
A common workaround: manually assign IDs, build an Excel traceability matrix, then calculate coverage from Excel. Convert Word docs to Excel rows, manually assign IDs, add "related requirement" columns, and fill in IDs.
2023: An OEM functional safety audit had assessors randomly check 13 traceability chains across 4,000 Excel rows. 5 had no matching files. 8 system requirements traced to the same architecture ID, which pointed to completely different architecture descriptions. Traceability strategy failed—project delayed 2 months.
3. Change Management Leaks
Baseline and change management are the 2 most complex processes in the V-model. In ASPICE 4.0, "Baseline" appears 32 times.
Example: A chassis control team's requirements, design docs, and test cases are frozen in Confluence V1.2. Development submits a change task in Jira. Since traceability lives in Excel matrices, finding affected items requires manually searching through each Excel. Result: HIL testing runs against the frozen Confluence V1.2 baseline, ignoring the change—missing test scenarios, bugs leak downstream.
Root cause: baselines and changes live in different places—no guarantee everyone gets notified.
4. Plugin-Driven Over-Engineering
Some of the above issues can be mitigated by purchasing plugins or custom development. But processes built on top of custom plugins face a harder choice when scaling up: keep compromising on this tool, or restart from scratch based on the V-model?
For example: How do you manage cross-project reuse? How do you do deeper analysis for functional safety and cybersecurity—HARA, FMEA, FTA, TARA—on top of normal requirements and architecture docs?
Conclusion
Jira's popularity in automotive, along with all these problems, points to one fact: tools are built on era-specific methodologies, and how well a tool implements a methodology makes a huge difference. General-purpose tools solve some problems but have gaps in vertical domain use cases.
ASPICE is fundamentally systems engineering, not project management. Simply importing a cross-domain software tool can't fully cover the automotive V-model lifecycle digital process.
As cars evolve toward consumer electronics and ASPICE fuses with Agile, we need both new methodologies and new software tools built for today's automotive development scenarios.
