Release date US: 2026/05/01
Release date AU/EU: 2026/05/01
Jama Connect® v9.35
Jama Connect MCP™
AI-driven development workflows often break down when engineering context is fragmented across tools, lack traceability, or can't be governed within regulated environments. Without a unified product graph and controlled access to specifications, AI agents produce inconsistent outputs, increase token inefficiency, and introduce compliance risk.
Jama Connect Model Context Protocol (MCP) extends Jama Connect into development environments that are AI-enabled, allowing engineers and AI agents to operate directly against governed, traceable product data. By exposing the Traceability Information Model through Jama Connect MCP, Jama Connect enables high-quality LLM inference, spec-driven development, and compliant automation across the software delivery lifecycle.
Key Benefits
- Enables spec-driven development by providing AI agents structured, versioned access to requirements and system context.
- Improves LLM inference quality and token efficiency with a consistent, complete product graph.
- Maintains end-to-end traceability between engineering artifacts and AI-generated outputs.
- Enforces permissions, workflows, and auditability for regulated development environments.
- Supports parallel development across teams, disciplines, and AI agents without loss of governance.
- Accelerates product velocity while preserving compliance and engineering rigor.
Feature Highlights
- Jama Connect MCP — Provides standardized access to Jama Connect data for AI-enabled tools such as Claude, Codex, Cursor, GitHub Copilot, and Visual Studio.
- Traceability-Aware Context Delivery — AI agents interact with a structured product graph, ensuring that outputs are aligned to requirements, specifications, and system models.
- Governed AI Access — Enforces existing Jama Connect permissions, lifecycle workflows, and audit trails within AI-driven workflows.
- Spec-Driven Development Enablement — Engineers and AI agents can iterate on specifications within a shared, version-controlled context.
- Cross-Discipline Integration — Supports multidisciplinary engineering by exposing unified context across software, hardware, and systems teams.
- Audit and Compliance Alignment — All interactions through Jama Connect MCP maintain traceability and support regulatory audit requirements.
Engineering Impact
- Parallel Development at Scale — Enables concurrent work across engineers and AI agents without compromising system integrity.
- CI/CD Integration — Supports automation of status changes across disciplines through pipeline integration.
- Live System State — Maintains an up-to-date representation of product development across branches and teams.
- Enterprise Scalability — Supports large-scale deployments with millions of items and relationships.
Availability
Jama Connect MCP is a separate-purchase add-on for Jama Connect cloud and self-hosted customers. Contact your Customer Success Manager for more information.
This release establishes the foundation for AI-Driven Development within Jama Connect by integrating governed engineering data directly into modern AI tooling ecosystems.
Updates from User Feedback
-
When creating a category, you can now add a description.
-
When a description is added to a category, it now appears as a tooltip when you hover over that category in the category tree.
-
When you duplicate an item, you can now include its categories in the duplicated item.
-
When an item is system-locked, the lock indicator in Single Item View now appears in blue to align with the rest of the application.
-
When you remove a widget from the dashboard, a confirmation window now appears so you can approve the deletion before the widget is removed.
-
Organization admins can now remove previously assigned colors from an entry and select any color using the color picker or by manually entering a hex value.
-
Test group layouts now provide more horizontal space for long test case IDs, making them easier to scan and reducing truncation.
- The Actions column in Admin > Organization > Reports now provides improved width and usability for easier interaction.
- You now receive a warning before high-risk move operations that might flatten the hierarchy, helping reduce the risk of accidental structural data loss.
- GET Activities now include reference ID context for created objects, making follow-up retrieval workflows more direct.
Minor Enhancements
- Performance for the Duplicate Project operation has been significantly improved, particularly for large projects. Projects with 50,000 or more items now copy in seconds to minutes rather than hours — up to 90x faster in testing at scale.
- Intelligent Rewrite performance was improved to reduce response latency and support a smoother authoring flow.
-
The Test Plan folder icon is now consistent with the folder icons used in the Test area of Jama Connect.
- Review index header badges now use a compact format.
End of Life — Option to Disable Versioning
In an upcoming release, the option to disable item versioning will be removed. This option has seen limited use and, in some cases, caused confusion or led to unintended loss of audit detail.
Coming Soon — Filter Trace View by Category
In an upcoming release, you will be able to analyze traceability with greater precision and focus by filtering across the entire Trace View based on category values. These improvements help reduce noise and improve efficiency.
- Filter the entire Trace View by category — View only items associated with one or more selected category values across all levels of the Trace View.
- Improve traceability focus — Remove unrelated upstream and downstream items that don't match the selected category.
- Streamline trace analysis — Reduce cognitive load and accelerate trace analysis by narrowing the view to only relevant items.
Datatap Incremental Exports
Datatap now supports incremental exports, enabling more frequent data deliveries — such as every 2, 4, or 6 hours. After an initial full baseline export, subsequent deliveries contain only the delta (changed or new records) since the last run, allowing jobs to be completed significantly faster. Customers are responsible for building scripts to ingest, reconcile, and model the incremental data on their end.
Resolved Issues
| ID | Description |
| SOS-DEF-8564 | In Document View, the View Settings field order is now preserved when you view items from a parent component. |
| SOS-DEF-8624 | When an invalid resource path is provided for GET/files/{url}, the REST API now returns the correct 404 error code. |
| SOS-DEF-9157 | When you edit an item from a review, release field information is now correctly displayed. |
| SOS-DEF-9261 | When you update a category path, it is now updated in the project. |
| SOS-DEF-9361 | In the REST API, GET /items/{id} now includes the version. |
| SOS-DEF-9398 | Adding or removing tags with a batch update on baseline items no longer generates an error. |
| SOS-DEF-9421 | When you update tags with a batch update, the Modified Date field now displays the correct results. |
| SOS-DEF-9474 | Baselines no longer display stale data when related resources are updated after the baseline is created. |
Comments
0 comments
Please sign in to leave a comment.