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

# Release Notes

## New Versions

* GitHub Enterprise: 3.18.10

## Enhancements

### TestRail

* Enhanced the TestRail integration to support changes introduced in TestRail.
  * Added support for TestRail fields updated from Markdown to Rich Text, ensuring formatted content continues to synchronize correctly.

### Jira Zephyr Scale Cloud

* Added support for configurable API base URLs in the Zephyr Scale Cloud plugin for Jira, allowing regional-specific endpoints to be configured and ensuring API tokens work correctly with those endpoints.
* For more details, refer to the [Zephyr Scale Cloud](https://docs.opshub.com/connectors/jirazephyrscale#system-configuration) documentation.

## Major Bug Fixes

### Common

* Improved OIM UI usability by resolving issues with alignment, button visibility, and audit log display.
* Resolved an issue where an integration remained in an **Active** state after being deactivated, resulting in a **"Job is not associated with this integration"** error when the integration was explicitly executed.

### MSDynamics

* Resolved an issue where status updates were not synchronized to the target system when MS Dynamics was configured as the source and the status was updated immediately after adding a comment.

### ReadyOne

* For ReadyOne as the source system, resolved an issue where a global failure stating **"Entity type information is missing"** occurred when a reference field pointed to a Poly Item that referenced a Requirement.


---

# 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.233/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.
