> 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.235/release-notes.md). # Release Notes ## Enhancements ### Common * Improved the performance of the failure analysis view when handling a large number of failures. ### ReadyOne * Added support to integrate with ReadyOne without service dependencies and with OAuth authentication. * Post-upgrade steps: [Migrating Version to 7.235 or Above](https://docs.opshub.com/v7.235/pages/FiQp5d9XMZJHrAkZAUux#migrating-version-to-7.235-or-above) * Enhanced ReadyOne reference field support to load lookup values, display reference names, unset references, and support references to the same entity type. ### HPQC * Added support to preserve the rank/order of HPQC Requirements during synchronization. ## Major Bug Fixes ### Aha * Fixed an issue where Aha To-Do display IDs were displayed instead of their display IDs in sync reports and the Remote ID field. * Resolved an issue where Aha Goal parent-child ("Contains goals" / "Belongs to goal") relationships were not available for relationship mapping in OIM. ### Azure DevOps Server/Services * Resolved an issue where synchronization failed with an **"Access is denied due to invalid credentials"** error when work item's rich text field contained attachments referenced from Azure DevOps Pull Requests. ### HPQC * Resolved an issue where HPQC comments were duplicated during backdated synchronization and updates to existing comments were not synchronized correctly. ### ReadyOne * Resolved an issue where ReadyOne synchronization failed when an entity was created or updated by a user with a blank or invalid email address. * Resolved an issue where ReadyOne reference field synchronization failed when the referenced entity had been updated after synchronization. --- # 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.235/release-notes.md?ask=&goal= ``` `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.