Rich text features to some of the WF native fields, specifically Issue Descriptions? Switch current custom text fields to rich text?

Hi Kristy, We at Truist certainly hope there are no plans to do this. We’d prefer these “Rich Text” features not be implemented at all because they result in quite useless data from a reporting perspective and we don’t need them. Switching native fields to this format would be disaster. And now as configuration experts, we have a field type that we have to explain away as something that shouldn’t be used when people ask “what’s that?” as we build forms. If you don’t believe me on the useless front, try building a view that renders that “Rich Text” in a report and see how it looks. The only value I see is in the amount of data you can store in a field, which just screams “more useless data!” to me that I still can’t render in a view. What’s the point? It’s time we stop trying to bend Workfront to do what it’s not meant to do by adding ideas we all don’t need but that a few of us really want. Narayan (Truist)