Yes please! When the new resource budgeting tools were first coming out, it was sold that we'd first have all the previous capabilities. It seems many of the things we were able to do with Resource Estimates didn't make the cut. Hopefully we get some of these important pieces back soon.

I like the general idea of improving the exported data. It seems to me that there are a lot of ideas floating around about what it should look like -- this makes me think that a customize-able approach would be best. Maybe to start we just get a dump of data that's easy to work with: standarized col...

I haven't played with this, but how does it impact multi-role users? I think the role is useful in that case?

When using the Adjust Budgeting Dates tool, when you drag the hours to another region on the timeline you should be able to click save.

Please give us this ability back!

At our organization, we've experimented with Web Data Connectors in tableau to have a place where our tableau server can get information directly from Workfront's API and build more advanced reports than Workfront is capable of producing for us (side note it'd be nice to be able to have a view into ...

We've seen this behavior at our company as well. There ability to attach certain forms is dependent on the user's access (forms can be limited by group and etc) and we've actually exploited it as a feature to automatically add custom forms when user's create issues or tasks without attaching the nec...

In the legacy API Resource Estimate objects, there was a field "scheduledHours" that would level assignment hours across a timeline on a daily basis between the planned start date and planned completion date of a task or issue. This functionality still exists in the application in both the Resource ...

It would be nice to have full functionality on the Resource Budgeted Hours, similar to what we had for the legacy Resource Estimate objects. This would include the ability to filter on all fields (including plannedBudgetedHours), access to the count function, and the ability to use $$LIMIT and $$FIR...

I think resource pools bucketed by role could give you a good view from the planner perspective.