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

# Release Notes

{% if "OM4ADO" !== visitor.claims.unsigned.product && "OAM" !== visitor.claims.unsigned.product %}

## New Entities

### Jama

* Bidirectionally sync the Releases entity

### SolarWinds Service Desk

* Bidirectionally sync the Task entity

## Enhancements

### Common

* Added support for API token-based authentication for OIM MCP Server and OIM Admin APIs
* Introduced a global sync report with a consolidated view across all integrations
  * Added OIM Admin API support to retrieve sync report data for offline analysis and reporting

### Azure DevOps Server/Services

* Added support to sync process parameters for Build Pipelines

## Major Bug Fixes

### Common

* Resolved an issue where field mapping could not be saved when mapping reference fields with more than 100 values
* Resolved an issue where the entity internal ID was displayed in the Remote ID/Link reconciliation.

### Jira

* Resolved an issue where inline attachments were not synchronized when rich text fields or comment were overridden using Jeditor.
* Resolved an edge case where work items could be linked to the wrong Jira issue during synchronization
  * In rare cases, when Jira delayed making newly created issues available in API.
    {% endif %}

{% if "OM4ADO" === visitor.claims.unsigned.product %}

## Major Bug Fixes

* Resolved an issue where Epics failed during migration when their Id matched a Release Pipeline ID in the same project
* Resolved an issue where Release Pipeline creation failed when projects were remapped, as it was linked to the wrong Build Pipeline.
* Resolved an issue where Build Pipeline creation failed when linked to a repository from another project

## Enhancements

* Added support to sync process parameters for Build Pipelines
  {% 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.228/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.