> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.239/release-notes.md). # Release Notes ## New Entities * IBM Engineering Test Management: Test Suite Execution Record ## Enhancements ### Common * Added a REST API (`/defaultXSLT`) to fetch default XSLT scripts for field mapping, supporting different field types and configurations, including default values and lookups. * Resolved an issue where remote links could break for entities that contained spaces or special characters such as &, #, or % (e.g., ADO Variable Group names, Polarion Test Run IDs, Gerrit project paths, and MBSE element/project names). ### IBM Engineering Test Management * Added the Test Environment field to Test Plan entities and the Test Environment and Iteration fields to Test Case Execution Record entities, enabling access to their details through advanced XSLT. ### ServiceNow * Enhanced ServiceNow synchronization handling to prevent failures when the ServiceNow load balancer returns repeated HTTP 429 (Too Many Requests) responses. ## Major Bug Fixes ### Common * Resolved an issue where purging integrations containing entity hierarchy information failed with a Hibernate **TransientObjectException**. * Resolved an issue where global failures caused by multi-entity polling were visible only at the integration group level and not on the individual integrations. ### MBSE * Resolved an issue where integration in current state failed to create entities with mandatory reference fields when the referenced entities had not yet been synchronized. * Resolved an issue where elements that became eligible for synchronization after being moved to a selected package or meeting the integration criteria were not synchronized until a subsequent update. ### qTest * Added support for qTest relationship mapping for Module-to-Test Case and Test Cycle-to-Test Suite relationships with reverse link options, enabling relationship synchronization from both entity perspectives. ### IBM Engineering Workflow Management * Resolved an issue in the EWM connector where custom fields with names matching standard OSLC attributes caused incorrect project scope validation, preventing eligible work items from being synchronized. ### Jira * Enhanced Jira synchronization to reduce memory consumption when processing large volumes of issues updated through bulk operations. ### HPQC * Resolved an issue where the Release Full Path field was not synchronized during current-state synchronization. ### Codebeamer * Resolved an issue in the Codebeamer connector where downstream reference links were unavailable for relationship configuration from the referred entity side. * Reference documentation: [Configure Downstream Reference Link Metadata](/v7.239/connectors/codebeamer.md#configure-downstream-reference-link-metadata) ### Aha * Resolved an issue where revision synchronization failed when multiple custom fields shared the same key but had different data types. ## Documentation ### GitHub * Updated the GitHub connector documentation to include documentation for Milestone Entity, Custom Fields, and Attachment Synchronization. * Reference documentation: [GitHub Documentation](/v7.239/connectors/github.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.opshub.com/v7.239/release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.