Keep Jira for delivery work if it is doing that job well. Its flexible issue model and workflows can track engineering tasks, but a regulated or complex product needs explicit requirement authority, hierarchy, change approval and verification evidence. The useful choice may be Jira alongside a requirements system, rather than replacing Jira. This is Arc's vendor-authored assessment.
When does issue tracking fall short?
Jira documents issues, workflows and links. Ask whether a reviewer can identify the accepted requirement revision, its parent, rationale, applicable product variant, verification method and evidence without relying on naming conventions or a marketplace add-on. If the answer is yes in a small project, keep the simple setup. If people rebuild a traceability matrix at every review, the engineering source of truth is missing.
Which tool should hold engineering records?
Arc connects system requirements, interfaces and verification for space work. Jama Connect supports formal review and traceability. Polarion or Codebeamer can be appropriate where software ALM and enterprise lifecycle governance need one platform. A well-governed document or spreadsheet can suffice for a short, stable list with one owner. Compare each option against the same source records, including any Jira app currently supplying requirements features.
What should Jira own?
For a synthetic flight-software timing requirement, keep the approved “shall” statement and verification criterion in the engineering authority. Let Jira own implementation tasks and defects. Link the task to the requirement by stable ID, define how changed acceptance criteria are approved, and record which system owns the test result. A Jira issue closed as “done” must not silently become requirement verification.
What should handover and exit preserve?
Create one requirement change, one implementation ticket and one failed test. Check that the link is navigable in both directions and that the failed result reopens the right engineering decision. Export the records and confirm the link's meaning remains intelligible. Count manual duplication between systems; it may outweigh the benefit of a new tool.
Where does Arc fit?
Arc can provide the engineering programme record while Jira remains the delivery tracker. Integration details depend on the selected deployment and workflow; define authority and reconciliation rather than assuming every Jira field synchronises natively.
Frequently asked questions
Can Jira manage requirements by itself?
It can support a lightweight list, especially with configuration or apps. Prove baselines, typed traceability, formal review and verification evidence for the actual programme.
Should Jira be removed when a requirements tool is adopted?
Often no. Jira can continue to own tasks and defects while the engineering tool owns approved requirements and their verification context.
What should a pilot include?
A requirement change, implementation issue and failed test, with clear ownership of each record and an inspectable link between them.
Evaluate these programme criteria in Arc
Arc connects requirements, systems and interfaces, controls branch, review and merge, and links verification evidence to the relevant requirements and configurations. Evaluate one representative work package against this guide’s criteria.
Luc will email from luc@archelps.com to arrange setup. Agree scope and data handling before adding programme information.