Can we get an update on this? It is NOT delivered. Mucking up your calculations and making it even harder to fix them is NOT a solution.I've just had a client ask me why "an alleged enterprise project management system can't do what I can do in a simple spreadsheet in five minutes". They want use...

In my testing, simply changing the task status populates the commit date and overwrites projected dates, which has a knock-on effect on subsequent tasks. Work on it does it because it also changes the task status. So unless we remove the ability to change task status (!), adding or removing things...

I absolutely refute that this has in any meaningful way been delivered. Sure, you can hide the 'commit date' but as soon as a worker clicks 'work on it' it over-rides the projected date with the commit date anyway, only now you can't even edit it. It hasn't fixed the problem of removing commit dat...

Jeremy, could you provide more details on how, when I'm looking at a proof in the proofing viewer, I can see information about the task and/or project the proof is associated with (including information on custom forms attached to the task and/or project)? I'm not aware of anything in 20.3 or 20.4 ...

Currently, any planner creating a project can see every single job role in the Workfront instance. Across a large organisation, this can be an extensive list with many similar job roles. It would be great if job roles could be global (as is) or associated with a specific group, and only members of...

Mainly voting for number 1 above. You really should enter each point above as a separate idea - makes it much easier for people to find and vote on your suggestions.

Since a lot of instances don't even use companies, another way to achieve this would be at the template level to not only include or exclude the built in fields, but determine if they are mandatory or optional.

So this could be resolved bya) Letting someone belong to more than one Company or;b) Associating Companies with groups (like statuses and approval processes are)

Or how about when you specify fields to add to a card, specify if it's 'always' visible or only when expanded. Achieves the above functionality, but can be more flexible for other use cases. You could even disable the built in fields (like % complete which gets a lot of requests) and replace that ...

It would be great if users had an option to auto-assign tasks for the duration of the project. Ideally, this would be an option after '6 weeks' in the schedule when only one project is showing that would dynamically set the number of weeks to match the project planned start and end dates. However,...