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

# Release Notes

{% if "OpsHub Integration Manager" === space.vars.SITENAME %}
\---

## Enhancements

### Azure DevOps Server/Services

* Markdown formatting for rich text fields and comments, including inline images and mentions, is now supported for Pull Request entity.

## Bugs

### Common

* Entities were skipped during reconciliation in multi-project integrations where multiple source projects were synchronized into a single target project.
* Unexpected link removal during backward synchronization in out-of-scope re-scope scenarios.
  * Use case: When an entity and its linked items moved out of scope in System 1, the corresponding entities in System 2 were removed. After the project was brought back into scope in System 1 and the entity was recreated in System 2, backward synchronization treated the missing links as removals and incorrectly removed the valid existing links in System 1.

### Codebeamer

* For Codebeamer as the target system, the link sync between Defect and Test Run failed with the following processing failure error message: `OH-Connector-0055: Error occurred while performing operation on Link of the entity. Because of java.lang.NullPointerException: Cannot invoke "java.util.List.stream()" because "mandatoryLinksLst" is null".`

### IBM Engineering Test Management

* For IBM Engineering Test Management as the source system, synchronization failed with the following processing failure error message:`Caused by: org.xml.sax.SAXParseException: The content of elements must consist of well-formed character data or markup.`. This occurred if the entity contained the complex field \[like "Approvals" field].

### GitHub

* For GitHub as the source system, project information was not retrieved during Issue entity synchronization.
  {% endif %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.opshub.com/v7.213/release-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.