> 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/release-notes.md).

# Release Notes

## New Versions

* EWM: 7.0.3

## New Entities

* MBSE: Project
* Polarion: Plan and Test Run

## Enhancements

### GitHub

* Added support for GitHub Pull Request state history, enabling synchronization of state changes with their corresponding timestamps and user information.

### Aras Innovator

* Added configurable versioning control for Aras synchronization through the new **OH\_Version** mapping field.
  * This field allows users to skip creating new versions and update the current version based on custom mapping conditions.
  * Reference documentation: [OH\_Version](/connectors/aras.md#version-control-of-aras-innovator-items-oh_version)

### IBM Engineering Requirements Management DOORS Next

* Added support to synchronize the hierarchy and ordering of artifacts in DOORS Next Modules, enabling the structure and artifact order to be preserved in the target system.

### MBSE

* Improved MBSE tag and link synchronization performance by approximately 91% by reducing redundant API calls.

## Major Bug Fixes

### IBM Engineering Test Management

* Improved synchronization performance when entities contain multiple lookup fields.

### Jira

* Resolved a global failure where synchronization failed with an **ArrayIndexOutOfBoundsException** when Jira history contained sprint names with commas.

### qTest

* Resolved a processing failure stating **"Module does not exist"**, where synchronization to qTest as a target system failed while updating the qTest Module hierarchy when a source Folder containing Requirements was moved to a different parent Folder.

## Documentation

### IBM Rational ClearQuest

* Added documentation for the ClearQuest API character limit on multi-line text fields.
  * Reference: [ClearQuest Documentation](/connectors/ibm-rational-clearquest.md#api-response-length-setting-for-multiline-text-fields)


---

# 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/release-notes.md?ask=<question>&goal=<user_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.