Release date US: 2026/05/19
Release date AU/EU: 2026/05/19
Jama Connect® v9.35.x
Model Context Protocol (MCP) Server
AI-driven development workflows often break down when engineering context is fragmented across tools, lacks traceability, or cannot 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.
The Model Context Protocol (MCP) Server extends Jama Connect to AI-enabled development environments, allowing engineers and AI agents to operate directly on governed, traceable product data. By exposing the Traceability Information Model through 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
- MCP Server for Jama Connect — 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 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
MCP Server 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.
Categories Tree Now Visible in the Manage Categories Page
We’ve improved the Manage Categories experience! You can now view the full Categories list in a hierarchical structure when applying Categories from List View or Single Item View.
Benefits
Better visibility into category hierarchy
Faster category selection and management
Improved usability for complex category structures
Enhanced Test Management Activities
We upgraded several areas of Activities to provide clearer insights into the changes your teams make, helping you work with greater control, accountability, and confidence.
What's improved
- Increased visibility into team actions — Easily see who did what and when, reducing the risk of errors or unauthorized changes.
- Stronger audit trails — Stay audit-ready with detailed activities that support key compliance standards like ISO or FDA.
- Faster troubleshooting — Quickly trace and resolve issues or discrepancies with richer, more structured activity data.
- Built-in accountability — Transparent tracking helps teams maintain consistent, compliant, and high-quality processes.
Benefits
- Makes it easier to maintain trust
- Helps meet compliance requirements
- Keeps operations running smoothly
- Improves day-to-day visibility
- Enhances decision-making
Project-level Activity Stream
Stay on top of key project activities with new filtering and tracking options.
- New Filters — Quickly focus on specific activity types with filters for Test Plan, Test Cycle, and Test Run.
- Updated Activities — More detailed tracking for “Plan sent to review” and “Delete Plan” actions.
- New Activities — Activity now includes “Archiving” and “Unarchiving a Plan” events for better lifecycle visibility.
Test Plan Activity Stream
Easily track changes within your test plans to improve oversight and accountability.
- Updated Activity — Improved detail for “Plan sent to review.”
-
New Activities
- Add or delete groups
- Add cycles or bulk-add runs
- Delete cycles or bulk-delete runs
- Manually delete runs
- Add or delete defects
- Add test cases to a plan
- Archive or unarchive plans
Test Case Activity Stream
Get full visibility into how your test cases are used.
- New Activity — See when a test case is associated with a plan, making it easier to trace test coverage and changes.
A Note About Test Management Updates
As a result of these changes to the Test area of Jama Connect, if your organization utilizes our /activity endpoints, some activities will appear slightly different.
- Create cycle and delete cycle logs will have their itemType changed from the containing testCycle to the containing testPlan and the item ID will point to those respective items.
- Batch delete test run logs previously had no itemType value. These will now point to the containing testPlan as well.
- Several new activity logs will appear corresponding to the increased logging we've added.
Monitoring REST API Usage Activity
Organization admins now have the ability to see which users are using the REST API and the volume of calls they are making.
Benefits
- Improved transparency — Give organizations a clear view of how their applications and users are interacting with the system, including volume and timing of usage.
- Enhanced accountability — Associate REST API calls and the owners of OAuth ClientIDs, making it easier to trace usage, audit activity, and manage permissions.
- Increased operational efficiency — Quickly identify and resolve issues such as rogue integrations or applications/users making excessive or unexpected REST API calls.
Note: Data for REST API User Activity will only show usage information starting from the date the feature was enabled. Historical REST API usage data prior to that date won't be available.
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 includes reference ID context for created objects, making follow-up retrieval workflows more direct.
- Intelligent Rewrite performance was improved to reduce response latency and support a smoother authoring flow.
- To reduce confusion and conflicts with the configured Traceability Information Model, the Switch Direction option has been removed from the Single Item View's Visual Layout.
-
The text in the Add related drop-down menu is now easier to read.
- Moderators are now clearly alerted when finalizing a review that contains items rejected by Approvers.
New Review Center REST API Endpoints
We're excited to announce the addition of Review Center REST API endpoints to Labs. These endpoints allow you to build custom monitoring solutions or integrate with existing tools to track review progress for in-flight projects, empowering teams to identify bottlenecks, improve quality control, and make data-driven decisions that enhance project efficiency.
| Endpoint | Description |
| GET /reviews | Get all reviews in the project with the specified ID |
| GET /reviews/{reviewId} | Get review by ID |
| GET /reviews/{reviewId}/comments | Get review comments |
| GET /reviews/{reviewId}/revisions | Get all revisions for a review by ID |
| GET /reviews/{reviewId}/revisions/ {revisionId} | Get the revision with the specified ID |
| GET /reviews/{reviewId}/revisions/ {revisionId}/participants | Get participants for a specified revision |
| GET /reviews/{reviewId}/revisions/ {revisionId}/progress | Get revision progress by revision id and review ID |
| GET /reviews/{reviewId}/revisions/ {revisionId}/revisionitems | Get revision items by revision ID and review ID |
| GET /reviewmoderators | Get all moderators for reviews |
Updated to Advanced Filters
This release includes additional options for refining filters focused on Categories.
The new options include:
- "Is under"
- Includes items assigned to any child category below the selected category in the tree view.
- Excludes items assigned to the selected parent category.
- "Is not under"
- Includes items not assigned to any child category of the selected category in the tree view.
- Includes items assigned to the selected category.
- Includes items with no assigned category.
Performance Safeguards for Large-scale User Actions
To ensure the performance of Jama Connect, we are introducing safeguards to protect your instance from costly user actions. These safeguards provide direction to users attempting large-scale actions that could adversely affect the performance of your instance. An example large-scale action is a bulk update to 5,000 or more items. In addition to introducing these safeguards, we are further elevating Jama Connect's industry-leading scalability.
Safeguards introduced in this release:
- Move in Project Tree — 25,000 (up from recommendation of 5,000)
- Move between projects — 5,000 (up from recommendation of 250)
- Reuse from project — 50,000 (up from recommendation of 5,000)
- Convert items — 1,000 (up from recommendation of 250)
- Office Template Export — 100,000 (up from recommendation of 25,000)
The safeguards introduced for Review Center are a mix of customer requests to help guide users in reasonably sized reviews, ensuring the best performance experience: a review targeted to a subset of content with a group of participants that can provide the necessary feedback.
- Items — 5,000 (up from the recommendation of 250)
- Participants — 100 (up from the recommendation of 50)
Note: Only new reviews must conform to the new safeguards. Existing reviews that exceed the new safeguards can continue.
System Health Report: Performance and Scale Updates
The System Health Report instructions now clarify that thresholds are intended to help organization admins monitor areas of high activity, not to limit project size.
Filter Improvements for Test Type Items
You can now find the exact test information you need, faster, more accurately, and with greater confidence. These improvements help reduce risk, improve test quality, and help you make better release decisions.
Improvements
- Filter items per location in an embedded filter — Review items related to a given location.
- Find Test Plans containing a specific Test Case — Understand where a test case is being used.
- Find Test Cases contained in specific Test Plans — Review the scope and coverage of a given test plan.
- Filter by Test Case Status within Test Plans — Identify test cases that are unscheduled, blocked, failed, or in other key states.
- Keyword search in Test Steps (contains word) — Find test steps based on specific wording, making steps findable.
- “Has no steps” filter for Test Cases and Test Runs — Identify incomplete tests that are missing execution steps.
- Filter Test Runs by Test Cycle and Test Plan — Locate executions tied to a specific planning context.
Note: You can now filter for a list of test cases that are associated with specific test plans.
Trace View Improvements
Filter Trace View by Category
You can now 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 do not match the selected category.
- Streamline trace analysis — Reduce cognitive load and accelerate trace analysis by narrowing the view to only relevant items.
Improved Readability
This release introduces Trace View improvements that enhance daily usability and reduces friction when reviewing trace data.
The Trace View grid now includes more detailed information, while retaining the context of the big picture for focus and efficiency. You can now review traceability data more efficiently with clearer layouts, readable long text on hover, and more intuitive visual indicators — all without leaving Trace View.
-
Access to complete truncated info
- For every visible table cell and header, hovering provides complete plain text. You can now read long names and descriptions without navigating away from Trace View.
-
Optimized default column width, allowing for more space for important data:
- 2-digit columns for the number of attachments, links, comments, connected users, and upstream and downstream relationships.
- Compact column for lock status now uses new padlock icons to differentiate user-locked items from system-locked items (replacing previous "true" and "false" status).
- Columns now accommodate global day-month year formats that include dates (created, modified, last activity, last locked) and are set at 80px.
Admin Notes
Upgrading from Jama Connect 9.22. x or 9.28. x
Jama Connect now uses OpenSearch for indexing and search instead of Elasticsearch. Before upgrading, remove the existing labels from the Elasticsearch StatefulSets and PVCs, delete the existing labels from the Elasticsearch nodes, and record the Elasticsearch settings from the KOTS Admin Console. The upgrade process removes these settings, and you will need them later when updating the OpenSearch settings. Instructions for completing these steps are included in the Jama Connect 9.35.x User Guide.
End of Life — Option to Disable Item Versioning
In the next self-hosted release of Jama Connect, the option to disable item versioning will be removed. This option has seen limited use, and in some cases, it caused confusion or led to unintended loss of audit detail.
End of Life — Crowd Support for Jama Connect Self-Hosted
Atlassian has announced end of life for its Data Center products, including Crowd, and new Crowd licenses are no longer available for purchase.
Aligned with this decision, Jama Connect 9.35 is the last release to support Crowd authentication for self-hosted deployments. Crowd settings will be removed from Jama Connect in the 9.41 self-hosted release.
Customers currently using Crowd should plan to migrate to a supported alternative before upgrading to the Jama Connect 9.41 self-hosted release.
Resolved Issues
| ID | Description |
| SOS-DEF-493 | The default sort order is now applied when viewing baselined items in List View. |
| SOS-DEF-2664 | The default sort order is now applied when viewing baselined items in List View. |
| SOS-DEF-4110 | During round-trip import, the multi-select field is now cleared when values are removed from the source spreadsheet. |
| SOS-DEF-4706 | The default sort order is now applied when viewing baselined items in List View. |
| SOS-DEF-4897 | When you reuse one item, it now appears in the Activity Stream. |
| SOS-DEF-5534 | The Test Case item type "is empty/is not empty" condition now returns the correct results for the Steps field. |
| SOS-DEF-5894 | When you select all items in List View, the Manage Categories option now appears when you have more than one page of items. |
| SOS-DEF-6880 | The Visual Layout for Single Item View no longer includes the Switch Direction option. |
| SOS-DEF-6962 | Swagger is now correctly documented for POST endpoints. |
| SOS-DEF-7119 | From the REST API, a user with multiple Project Admin privileges can now unlock a locked item. |
| SOS-DEF-7244 | The asterisk (*) sign is now correctly displayed for the mandatory versionNumber field in Get /items/{id}/versionedcategories. |
| SOS-DEF-7282 | When creating a filter, picklist options with long titles are now correctly displayed. |
| SOS-DEF-7371 | The asterisk (*) sign is now correctly displayed for the mandatory baselineId field in GET/items/{id}/baselinedcategories. |
| SOS-DEF-7428 | The versionNumber field is now labeled as required on the Swagger page, and GET requests to the /items/{id}/versionedcategories REST API endpoint are now successful. |
| SOS-DEF-8339 | Tags are now updated correctly when you batch edit filter results that span multiple pages. |
| SOS-DEF-8563 | A discrepancy in the Swagger Example Response Schema for /labs/items/batch has been resolved. |
| SOS-DEF-8564 | In Document View, the View Settings field order is now preserved when you view items from a parent component. |
| SOS-DEF-8737 | You can now upload .dbc file types after you add .dbc file extensions to the Allow List. |
| SOS-DEF-8796 | When you delete the default value from a pick list and use it on the x-axis of a matrix, the results are no longer rendered as "undefined undefined." |
| SOS-DEF-8847 | You can now append .rar attachment to an item. If needed, contact support to have the extension added to the Allow List. |
| SOS-DEF-8880 | A category can now be deleted after associated items are deleted. |
| SOS-DEF-8935 | REST API Swagger now correctly shows required fields for GET /users. |
| SOS-DEF-8994 | Filtering by the Steps field now produces the correct results for test cases and test runs. |
| SOS-DEF-9104 | When you use Excel Roundtrip for custom and predefined date fields, time information is now included and version issues no longer occur. |
| SOS-DEF-9109 | Baseline Comparison in Document View now shows differences between versions of documents on page 2 and beyond for baselines with more than 50 items. |
| SOS-DEF-9138 | Now, when you edit test cycles after deleting or re-creating test groups, duplicate test cases in a test cycle are no longer created. |
| SOS-DEF-9179 | The blue lock icon is now correctly displayed for system-locked items. |
| SOS-DEF-9194 | In Document View, when comparing baselines, you can now scroll horizontally to see complete rich text tables. |
| SOS-DEF-9208 | Duplicate relationship rules within the Traceability Information Mode no longer block updates to the rule. |
| SOS-DEF-9238 | From the REST API, the False Flag Field is now included in "Get Items." |
| SOS-DEF-9288 | The Organization Admin setting Include Item Type Key in Global ID is now retained after a page refresh. |
| SOS-DEF-9305 | System-locked items are no longer set as "user-locked" from the REST API. |
| SOS-DEF-9330 | REST API Swagger now correctly indicates that avatarUrl is not included in the GET /users response. |
| SOS-DEF-9334 | REST API GET /users and /usergroups responses now include the Type field as indicated in Swagger. |
| SOS-DEF-9361 | The REST API GET /items/{id} now includes the version. |
| SOS-DEF-9384 | The REST API getRelationshipsInProject method no longer incorrectly sets the isolation level to REPEATABLE READ. |
| SOS-DEF-9391 | Editing items in Document View no longer causes latency, including in containers with many items. |
| SOS-DEF-9474 | Stale data is no longer displayed in baselines when related resources are updated after the baseline is created. |
Comments
0 comments
Please sign in to leave a comment.