Thanks @Sven-iX, we are aware of and doing all of the things you've suggested. Our AM has not responded to us either on several issues, and we're currently drafting another list of our concerns to send in.

I can confirm that our team has been facing significant challenges with Support overall. There are many incredible people on the Support teams who still give us the same top-notch help as they did in the previous years. However, there is an increasing number of what seems like new employees who make...

I agree. I will say it's not a huge deal for my org personally, but it's just an unnecessary complication. It's strange that I can add brand new users to Workfront with full system administration privileges, but I can't set them up to be able to contact Support. Feels more like "You must now manage ...

As of at least this morning, I've noticed this suggested behaviour has been implemented.

Similar-ish to @nryan2, except I don't have the option for "Support administrator" at all, only "Product profile administrator". I also don't see "Support administrator" on my own profile, yet I am still able to open tickets as expected. Why is this?

For what it's worth, I get screen "bounce" frequently within the Workfront UI if I'm at 100%. If I change to 110% or 90%, it stops bouncing. Very frustrating experience.

It's a consideration because we've been trying to amalgamate an "unbridled" array of fields that are redundant, used across different areas of our org who each had their own system administrators - it's not so much "we don't need this data point anymore". Other consideration is cleaning up the long ...

I'm fairly confident that custom fields not being used on any custom forms no longer hold any data, and can therefore be deleted without much consequence. What are others' experiences with this? The only thing I can think of us that they may be used in Views/Filters/Groupings or Reports and just sho...

This is absolutely bonkers to me. I'm just experiencing this right now as well. What is the point of creating this field so that it lives in the field library, if the contents of said field won't be honoured in whichever custom form we use it in? Makes no logical sense in my humble opinion. We alrea...

Update: the issue has been fixed. It hasn't helped my existing Views with this conditional formatting, but I can successfully create a NEW view, apply the "entire row" formatting, and then remove it thereafter.