In the TestRun page, the linked Coverable Issue and Defect keys are strikethrough-ed when the linked issue's status category is Done, even if the issue is not resolved (Resolution = Unresolved)

Description:

In the Test Run page, Xray applies a strikethrough to the Coverable Issue's key/Defect Issue's Key whenever the linked issue's workflow status belongs to the "Done" status category. However, native Jira only applies a strikethrough to an issue key when the issue is actually resolved (i.e., the Resolution field is set to a value other than "Unresolved"), independently of the status category.

In company-managed projects, an admin can configure a Done-category status without a "Set Resolution" post-function on the transition into it, resulting in issues that are Done-category but still Unresolved. Jira does not strikethrough these issues anywhere in its UI, but Xray's Test Run window does — this is inconsistent with Jira's native behavior.
 

Pre-conditions

• A company-managed Jira Cloud project.
• A workflow where the transition into a Done-category status does not include a post-function to set the Resolution field.
• A Requirement-type issue (e.g., Story) and a Defect (e.g., a Bug) using that workflow, linked to a Test issue via the Test/Coverage link.

How to reproduce

1. In a company-managed project, edit the workflow used by the Requirement and Defect issues.
2. Select the transition leading into the Done-category status and remove/skip the "Update Issue Field → Resolution" post-function on that transition. Publish the workflow.
3. Create a Story issue and transition it to that Done-category status.
4. Confirm on the issue itself that Resolution = "Unresolved" while Status category = Done.
5. Confirm in native Jira (e.g., Linked Issues panel on another issue) that the Story's key is not struck through.
6. On the TestRun page, observe the Requirement issue and Defect issues under the Test issue links.

Actual result/Attachments

The Requirement and Defect keys are shown with a strikethrough in the Test Run page, despite the issue being Unresolved.

Expected result

The Story's key should not be struck through in the Test Run window, since it matches Jira's native behavior of only striking through resolved issues (Resolution field set). Xray should check the Resolution field state rather than the workflow status category.

Version

• Xray Cloud 16.19.0

Workaround N.A