> 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

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

## Enhancements

### Jira

* Added support for Jira Service Management (JSM) Assets as reference fields, enabling Asset relationships to be synchronized and maintained across integrated systems.

### Tosca

* Added support for mapping Parent Folder as a reference field, making it easier to manage parent-child folder relationships using value mappings or default values.

### Azure DevOps Server/Services

* Now you can synchronize work items based on attributes of their linked items, enabling more targeted migration and synchronization scenarios.
  * Example: Synchronize only Tasks that are linked to a Bug with Priority = 1

### ServiceNow

* Enhanced support for inline images embedded using ServiceNow image links.

## Major Bug Fixes

### Common

* Resolved an issue that could cause high memory utilization during prolonged synchronization operations, resulting in improved application stability and more efficient resource usage.

### MBSE

* Resolved an issue that lead synchronization failures when reference fields contained relationships to unsupported or unavailable entity types. Synchronization now continues reliably even when related entity type is missing .

## Documentation Updates

### Redmine

* Updated the Product documentation for Redmine system to specify support for Redmine versions up to 3.4.x and avoid ambiguity regarding newer releases
  {% endif %}

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

* Resolved an issue where Shared Steps were not preserved during ADO-to-ADO Test Case migration. Shared Steps now retain their original structure and execution details after 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/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.