Hi Everyone,
Thank you for sharing your votes and comments on this bug.
The strikethrough behaviour in Jira is now consistent across all components within Jira.
The appearance of strikethrough text in Jira is now triggered by the "Resolution" field of an issue. Once an issue's "Resolution" field is set, the corresponding issue key will be displayed with a strikethrough.

If you wish to customize your workflow to determine the conditions for applying a strikethrough, please refer to our product documentation page page for instructions on how to update this behaviour. Most instances should see this change now however, enterprise instances might take a few more weeks.

Once again, thank you for your valuable feedback. I'll close this bug now.

Best regards, Ahmud

Hi Everyone,

I'm Ahmud, a product manager working on the issue view in Jira Cloud. Thank you for sharing your votes and comments for this bug. We have reviewed the behaviour of when a strikethrough is displaying on a linked issue.

We have updated the default behaviour for linked issues to display when the status is transitioned to "Done". You can read more about this on our product documentation page. We have also provided instructions on how to customise your workflow so a strikethrough only appears when the status AND resolution field is updated.

We understand this behaviour is inconsistent across multiple components in Jira Software. We are looking into bringing a consistent definition of done across Jira in the near future.

Regards, 

Ahmud 

Issue Summary

Linked issues are strikethrough when it is transition to Done status category without resolution

Steps to Reproduce

1. Have a project with 2 issues (A and B)
2. Add a status with "Done" category and make sure no "Resolution" set
3. Link 2 the issues with any link (ie. Blocking)
4. Transition one of the issues (issue B) to the above status so it's in "Done" category status without any Resolution value set.
5. Open the other issue (issue A) and notice linked issue (B) is strikethrough
   • Old issue view
   • 
   • New issue view
   • 

Issue Summary

Transitioning issues to statuses of status category Done results in Strikethroughs in the parent issue child list while the resolution field populated should be the reason for it instead.

Steps to Reproduce

1. Have a transition to a status of Done category that doesn't populate the resolution field in your workflow
2. Create a child issue
3. Transition the child issue to the respective status of your workflow mentioned earlier
4. Check the parent issue view and notice the strikethrough in the issue even though there is no resolution set

You might need to refresh the page to see changes.

 h3. Expected Results
Strikethrough should be added only upon resolution field filled in and removed if resolution field is cleared as well.

Actual Results

Strikethrough considers status category of the current status of the issue 

Workaround

See the parent issue using the Old View while still available.