The Issue ID is automatically crossed-out when creating a new issue in the backlog.

[Doug Henderson]

When a new issue (story, task, epic) is created in the backlog, the Issue ID already has a strike-through line. This is a new occurrence. The project workflows and fields are shared by many projects. I recognize that someone in a shared project changed the resolution status configuration of new issues to cause this, but I cannot figure out how to fix this situation. I welcome any guidance.

[Nic Brough -Adaptavist-]

I suspect one of your administrators has mistakenly placed the resolution field on the create (and possibly edit) screen for the issue.  When the resolution is on an update type screen, it will get set when the user commits.

[Daniel Tomberlin]

I have this issue too and did find Resolution on the screen used for Create/Edit. When the Resolution field is shown on the profile of an issue screen you'll then see the issue number crossed out on a Kanban board too.

Some issues under the same project will have the Resolution field displayed next to the status button and some will not. Those issues displaying the Resolution field were most likely issues created after the update to display this field on the aforementioned screens were made. There is a default for resolutions, but I think that default is not committed until a form is updated with that field on it as you explained Nic.

That said, removing the field will not update what was committed and thereby the strike-though will still be present. It's a bit annoying at first glance that these have a line through them. They are harder to read, give off the wrong message, and apparently cannot be uncommitted to a value after the fact.

I do liked being able to see it on an issue profile as it gives more detail to the status closure, which after removing the field from those screens I still present on the profile, so I guess they will still show, but only after the issue is closed, where the field exists to commit a value.