strikethrough issue

[laknath]

whenever I assigned an epic to a story, the JIRA number get strikethrough (as below) but in some cases, this doesn't happen. Please let me know why this is happening. 

[Pete Singleton · Accepted solution]

The strikethrough indicates that the issue is "Resolved", i.e. the resolution field has been set.  This is different to the Status, so you need to check the workflow to ensure that the resolution is being set (or the user is prompted to set it) when the issue is moved to "Done".

[Stuart Rolland]

I have some issues with a strikethrough that are only marked as done but have not been manually resolved. The resolution field says done, but that happens automatically instead of manually. Maybe that's ok?

[Mirek]

Hi @laknath ,

On the screenshot I do not see any issue that is having a key that is strikethrough 

Usually a straightrough is when the resolution is set to something else tan Unresolved so if anything is related to that please check your workflow settings first or if you are having any customization (or scripts) also those.

[Patrick Henry]

This is so stupid. Please disable this "feature". I just want to be able to read the text of the issue ID without the stupid "strikethrough".

I have a status column that tells me the effing status. I don't need a stupid strikethrough "feature" to make it harder to read the stupid text.

[Tina Esmaeili]

It's interesting, in my case, under the epic, the "Live" (Done) issues are not strikethrough, even though their resolution is Done. But when I filter the "live" issues of that same project separately, they are strikethrough! 

[Shen Ao 申奥]

I encountered the same problem with yours, and it is not related to the "resolved" status like most people said... May I know if your problem got resolved?

[Mirek]

Not actually Resolved status but "Resolution" field.. It must have a value then Jira "knows" that the ticket is actually done.