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

# Release Notes

## New Entities

* Azure DevOps Server/Services: Delivery Plan
* Zephyr Enterprise: Phase

## Enhancements

### Azure DevOps Server/Services

* Added support for Defect-to-Test Result relationship synchronization.

### ReadyOne

* Enhanced ReadyOne Poly Item reference synchronization to prevent failures when the referenced entity has not yet been synchronized.

### Tricentis Tosca

* Added support for Tosca workspaces using the Tricentis Server repository type, in addition to SQL Server repositories.
* Enhanced Personal Access Token (PAT) authentication by adding an authentication user input to the Tosca system configuration.

## Major Bug Fixes

### Common

* Resolved an issue where the Metrics & Trends dashboard displayed the following error for a newly created integration that had not yet been executed: `OH-API-0002: java.lang.NullPointerException: Cannot invoke "java.util.Date.getTime()" because "lastRefreshedDate" is null`
* Resolved an issue where Metrics & Trends dashboard refresh operations failed in PostgreSQL-based OIM deployments with the following error: `ERROR: column "last_refreshed_at" does not exist`
* Resolved an issue where renewed SSL certificates for cloud-based systems were not automatically installed after editing and saving the system configuration.

### Jira

* Resolved an issue where inline images embedded in Jira rich text fields were not rendered correctly in HTML rich text fields in the target system.
* Resolved an issue where Jira Service Management Request Type values were not synchronized when multiple Jira fields shared the same schema identifier. This caused OIM to retrieve values from an incorrect field during synchronization.
* Resolved an issue where issue statuses were not updated correctly during failure retry processing after a previously unavailable Jira workflow transition became available.

## Documentation

### Jira Service Management

* Updated the Jira connector documentation to include the additional permissions required when configuring Jira Service Management as a source or target system.


---

# 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/v7.231/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.
