How to undo strike through on title for completed but not done strike through

[Shari Barrett]

How to undo strike through on title for completed but not done strike through.

This issue began this week.  We have an initial 'to be completed by' date set however there are follow up processes that need the card to remain active without a strike through including updating the 'to be completed by' date for the next step of the process.

Is there any way we can turn this function off for our Trello Boards?

• have attempted to remove 'due date', and re-add  with future date, strike through remains.

[Alex]

Hi @Shari Barrett - Like @Rasmus Wulff Jensen mentioned above its due to the update we made on the due complete feature. We've heard the feedback and are making a change to remove the strikethru treatment from the text. You should see an update in the next day or so. 

Thanks for your patience!

[Donna]

@Shari Barrett @Mike Stewart I have disabled the new feature showing up on the front of the card through the board menu, settings, complete Status....from there I created a custom field called 'Job Completed', and although an additional step, I now check box that new custom field inside the card and my automations have been reworked to shift the card to where I need it to go.  Once I have fully executed on everything I need to do with that card and it is 100% completed, I then enter inside the card and checkbox the date next to the description or simply click on the date on the front of the card which then turns green and puts a strikeline through the description.

[Mike Stewart]

This feature needs to be able to get turned off! It's completely messed up my workflow! I hope they can make that change soon or I'll need to try something else. 

[Rasmus Wulff Jensen]

It is due to a new feature: https://support.atlassian.com/trello/docs/mark-a-card-as-complete/

Part of the feature can be turned off, but not the strike-through part at the moment, but since there has been a big backlash to the strike-through the Trello team is addressing it so hopefully soon it will be possible to disable it 🤞