FIX Resolved an issue where selecting more than 50 projects for migration could lead to unintended deletion of easeReq project data.

EASE-22724, EASE-22571

FIX Resolved an issue where clicking the coverage issue count did not redirect users to the issue navigator.

EASE-22716, EASE-22743

easeRequirements now supports fully automated migration of app data from Jira Data Center to Jira Cloud using Atlassian’s official migration tool. This includes seamless transfer of requirement trees, baselines, coverage and traceability data, configurations, and export templates, significantly reducing manual effort and migration risk. Teams can now plan and execute their move to Cloud with greater confidence, leveraging a guided process that preserves existing structures and relationships.

To know more, refer to Migration Path from Data Center to Cloud

IMPROVED Improved user experience by adding scrolling option when navigating through a large tree during creation of configuration of the first column.

EASE-20288

FIX Added fixes to the following:

1. Using "$.path" in a JQL statement returns an empty file.

2. Adding “apply-template” inside another template causes an export error.

3. Exporting a backup baseline causes an error.

4. Using “selectedIssue.url“ inside the template, breaks the exported file.

EASE-22068, EASE-22271, EASE-22248, EASE-21850

FIX Fixed issue where selected display fields reset to empty when scrolling during baseline compare.

EASE-19753, EASE-20738, EASE-21746

FIX Fixed issue preventing users from adding links to issues on the right edge of the screen.

EASE-21252, EASE-21656