Steven - as others have states before me, thank you and your teams for keeping an open dialog to our needs! Not to pile on to this fun adventure - but after spending a couple days giving a hectic training demo to 50+ people in 4 different business units on the changes coming next week - in particula...

yes -- seems to be more Windows than MacOS though - so I assume its how WF is handling CSS. Same thing happened in production for our users a dew months ago... John Seitz DTCI | Disney |

Just to add my 2 cents some of my users have been asking for this feature for awhile some of my users will see this and say what Vic said "Yuck" (or some other other sounding word ha) was this listed in the release notes for reporting? That said I would like the option in the report builder to...

Not a popular opinion (at least with real world users) BUT Workfront can do pretty much everything Jira can do BUT BETTER! One BIG exception is that Jira is more of a marketplace platform than anything else. Meaning if you stop and look at what Jira WAS it's a simple application - heck it's not even...

Strange -- CL5 still shows 2019.3 and the link doesn't appear to open: John Seitz DTCI | Disney | ESPN

The way Workfront created the database structure each WF Type (Task, Issue, Project etc...) is a unique Database Table or "lund" in short the tables are not connected, this greatly increases speed and scalability of the platform. BUT pending on what data you are trying to build in there are a few wa...

This functionally would seem to be a day one item, no? Especially since Workfront is an Enterprise focused tool and many companies run on a fiscal calendar.

Not something I would need to do often. BUT A HUGE WIN and actually with the ability to do it, I might make some changes with users who I have told no to in the past. I assume the data captured prior will remain in the table for reporting?

Vazgen - as you know I am a huge supporter of the "Subject' change ;-) -- Just not this way, especially with no communication. A few of our more seasoned groups have user guides that call out Subject. And as many have hinted at above... many user's have entered their name. and not to pile onto this ...

I'd "settle" on the ability to have - custom field aliasing on a form so that the field names can more direct and to the point. When you have an enterprise wide instance of 2k+ users from many departments some field names become very UGLY - ability to rename SUBJECT from the request queue page.......