Issue Summary

We expect strikethroughs to represent an issue which has a resolution set, yet there's other situations where we might see a strikethrough even if we don't expect, such as an issue in the "Done" status, with child sub-tasks - Or temporary strikethroughs when setting an issue to a Done status. 

When the board is grouped by Epic, the epic key will only be shown with a strikethrough if it has a resolution AND is in scope for the board. If the epic itself doesn't meet the criteria for the board (e.g. not returned by the filter, status is not mapped to a board column, was completed > 2 weeks ago on a standard kanban board) and is only present because its child issue is on the board, it won't be shown with a strikethrough.

Steps to Reproduce

1. Set a green/done status to an "In progress" column for a board and transition an issue to that status. Notice the issue does not have a strikethrough.
2. Add a sub-task to the issue - and find the issue now has a strikethrough
3. Other scenarios where strikethroughs are temporary ( refreshing the page removes the strike ) 

Epic swimlane scenario steps:

1. Set board to group by Epic
2. Make sure the epic and child issue are both included in the board filter
3. Transition the epic to set a resolution value (if it's not already resolved)
4. Confirm the epic key is shown with a strikethrough
5. Update the board filter to exclude the epic, but not the child issue (e.g. add "issuetype != Epic" to the board filter)
6. Epic now appears at the top of its swimlane without a strikethrough

Expected Results

Consistent results in strikethrough behavior

Actual Results

Strikethrough behavior is not consistent, you may even see different behavior on the same issue in the backlog view vs the board view. 

Workaround

Utilize To-do and in-progress statuses where you can to avoid a lot of these inconsistencies