We would like to take this one step further, front end names should all be given a back end ID number. The ID number should then be used for API calls (and fusion calls), so that changes to the custom field front end name do not impact the call. Currently, any changes to a custom field name break an...

Believe many of the voters here will also be interested in better forecasting reporting. I've submitted an idea to Create Assigned Hours as a reporting object. An Assigned Hours report would function just like an hours report, but would be future looking. You would then be able to run forecast repor...

I've created my first idea: Create Assigned Hours as a reporting object. An Assigned Hours report would function just like an hours report, but would be future looking. You would then be able to run forecast reports on hours, revenues, costs and profits by week or month and the reports could be summ...

Our leadership would like to be able to use Workfront to forecast hours, revenues, costs and profits by month. Reporting on the Assignments object does not give project owners, resource managers or leadership information about daily/weekly/monthly totals of upcoming work for users. Under People, th...

I second James - please upvote this idea in the idea exchange so Workfront understands the volume of their clients facing this challenge. We're having a lot of issues with accurately calculating revenue over time for users that have received one or more roles changes. It is especially tricky when yo...

We require timesheets and have abnormal week rules, this was a huge source of confusion during adoption and gave users an excuse to say "timesheets are too hard in workfront. the old system was better". Timesheet profile's already know the day of the week the timesheet should start on, I hope it wil...

Our ideal scenario: Time off can have unlimited types determined by the admin at the timesheet profile level (ex: Vacation, Sick, Summer Friday) Time off types can be archived if they are no longer applicable WITHOUT losing the hours from the past (ex: no longer using Summer Fridays, new time off t...

We have users with a full list of projects and multiple tasks per project, this would be very helpful

Michael, I'm glad I'm not the only seeing this as a serious issue. Being able to track user data over time (role, rate, cost, manager, company) is essential for accurate calculations and reporting. We only launched Workfront a month ago so we haven't had role changes yet, but we will have promotions...

Edit: I found the area Jenna was referring to below - and have successfully started deleting unused fields from our library. Thank you Jenna! ----- Would also like to delete fields from the system (for when you create a field, then realize it already exists but with a slightly different name)