Issue key in Work Mode does not get strikethrough when done

Summary of Bug

Given the following situation - In GreenHopper 6.2.1, The Scrum board has Swimlanes configured to use 'Stories', and the issue has at least one sub-task. When the parent issue is resolved, the issue key would not be strikethrough

Steps to reproduce

1. Install GreenHopper 6.2.1
2. Configure the Swimlanes in the Scrum Board to use 'Stories'
3. Create a sprint, an issue (plus a sub-task)
4. Insert the issue (that has the sub-task) into the sprint, and start it
5. Resolve the sub-task, and resolve the parent issue
6. Issue key of sub-task would have strikethrough, but not parent issue

Additional Info

It seems that if the issue does not have a sub-task, then the strikethrough would appear as usual