When is Atlassian going to add a function that will allo the organisation to remove the "strikethrough feature" even if an issue has Resolution set or has a status connected to the status category "Done"?
I asked Rovo "How do I remove the strikethrough on separate statuses?", this is what I got in reply:
---------
Unfortunately, you can't selectively remove strikethrough from individual statuses within the Done category. The strikethrough is automatically applied to every status mapped to the "Done" category — it's an all-or-nothing behavior tied to the category itself, with no per-status toggle.
The only way to remove the strikethrough from a specific status is to change that status's category away from "Done." In the workflow editor you have open:
Click on the status you want to remove the strikethrough from (e.g., status
10041you currently have selected)In the status details panel, change the Category from "Done" to "In Progress" (or "To Do", depending on what makes sense for your workflow)
Save and publish the workflow
Keep in mind that changing the category affects more than just the visual strikethrough — statuses in the "Done" category are used by Jira for:
Velocity and burndown charts
Resolution tracking
SLA calculations
Release reports
So if a status genuinely represents completed work, it's best to keep it in the "Done" category and accept the strikethrough. If the status is more of a transitional state (e.g., "Ready for Deploy" or "Awaiting Approval"), moving it to "In Progress" would be both accurate and remove the strikethrough.
How to view the Keys should be up to the organisation to decide, not having the option of removing the strikethrough does not align with an agile work process.
Hi @Carita J Tsiantes you don't mention if you are using Jira Cloud or Jira Data Center, but I found JRASERVER-7211 for Data Center and JRACLOUD-7211 for Cloud to allow this configuration. I would suggest voting for and watching it for any updates.
There's about 100 votes for each at this time.
Hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.