5.5

If you're using Jira 10 and want to upgrade to Jira 11, a manual installation is required for the first time.
Download the Jira 11 compatible app version from the Marketplace.

Starting with this version, the dark feature key for the ReqIF feature will no longer function, and an easeRequirements Ultimate license is required to continue using it.

Other improvements

	Component	Issue Key	Summary

	Component	Issue Key	Summary
1	Coverage View	EASE-19971	Added hyperlink to issue count in coverage view column header that will redirect to the column’s issue list in the Jira issue navigator.
2	Detail View	EASE-21763	Added support for returning the correct issues when inline editing the issue picker custom field configured from Adaptavist ScriptRunner for Jira Behaviours.
3	Word Export	EASE-21511	Added support for tree Word export of external images inside and outside tables pasted from Excel on a JEditor rendered field.
4	Cloud Migration	REQ-29719	Added additional pre-migration app check for invalid API token for Data Center to Cloud migration. Check out https://easesolutions.atlassian.net/wiki/spaces/R4JC/pages/2338160647.

Other bugfixes

	Component	Issue Key	Summary

	Component	Issue Key	Summary
1	Coverage View	EASE-21938 EASE-21415	Fixed coverage view statistics showing 0% on all columns even when issues are displayed.
2	Word Export	EASE-21060	Fixed Confluence image not getting exported when resized in tree Word export.
3	Cloud Migration	EASE-22198	Fixed null item type causing migration error for Data Center to Cloud migration.
4	REST API Tree View	EASE-22407	Fixed missing child items and other errors when executing REST API 2.0 to move issues successively in the tree view: PUT /projects/`{projectKey}`/issues/`{issueKey}`/move/issue Refer to https://easesolutions.atlassian.net/wiki/x/hoDaVw.
5	Jira Compatibility	EASE-22365	Fixed bug preventing deletion of child sub-tasks when deleting parent tasks in Jira.
6	Baseline	REQ-30631	Fixed bug where editing the baseline name in the baseline list view created duplicate names within the same project and caused other validation errors.