I'd like the ability to simply set a flag light "inlinediting=no" when I want to turn-off inline editing on a specific column of information.We had to work-around some limitations in Workfront that tied the value of one field to another field so closely that I want to make sure that dependency kicks...

For similar reasons to the OP, the ability to graphically set-off a group of columns would be a big help.

I agree with the OP. We come from a world where XLS files are often output on 11x17, so we have some fairly comprehensive reports we have to recreate in Workfront. Having to break into smaller reports or do excessive left-right scrolling could be mitigated by a feature like this.

Yeah this is one of the QoL things that you don't notice until someone points it out, especially as the SysAdmin. It's literally the first thing I do when opening a project: hit the collapse button. This lets me open only what I need to deal with and focus on it.I see both sides, many may want it to...

I would like to see this not just to simplify API calls and text mode calculations, but also to simplify the interface for the user.I could use the same label/question across forms bu have a different backend field name to keep them straight. For example, we have "Project Type" but it means differen...

Another upvote for me; it's a headache that so many of the built-in fields we don't use, but the user has to scroll by them and we have to admonish them "just ignore this" or "don't touch these or you'll really mess things up."

In lieu of, or maybe as part of this Idea...Require Users to only create new Projects from a templatehttps://experience.workfront.com/s/idea/0870z000000PSAfAAO/detail...I would like the ability to modify the default "New Project" feature so that at least I can define what custom forms are attached.I...

Could also use this functionality for the same reasons as the submitter. We want people to follow process and always use a template, but some may accidentally or intentionally "cheat" by not using a template.

OMGpleaseThankYouYes.The workaround of putting all the vendor information as user info in WF (even though those contacts won't use the system) is really a non-starter because of the chaos and clutter.This is not the only need WF has for little sub-databases of project/process information as well as ...

TimeSHEETs certainly do their job of tracking work on a task, but to comply with state laws for hourly workers, we would like some way to get a timeCLOCK: that is, a way for a user to record start/stop on:Workday/shiftBreaksLunchWe looked at add-on solutions to Workfront by third party vendors, but ...