This is an issue for us as well. We need to have duration and planned hours for a queue request. Because of our volume, it may be a two week duration but only 2 hours of planned work. The current setting of 2 weeks = 80 planned hours is crazy.
I just simply don't understand why some custom fields are sortable and others are not. This is so frustrating. Users need to do multiple sorts on a report
I need to be able to archive (or hide or make inactive) reports without deleting them. I want a period of time, before deletion, to archive them so I don't prematurely delete a report that someone my still be using. This gives users a little time to see if they need those archived reports.
Yes, I need additional fields for reports. I love the idea of having more fields on the report level, instead of a custom form, but I'd settle for a custom form if it gets us this functionality faster.
We are looking for similar suggestions/guidance. We want to create purchase orders based on job estimates and include fields that exist in WF then export into PDF. We need to be able to do several POs off of one project though.
This is an issue for us as well. We may have a task that has a duration of 20 days where the assignee needs to work heavier hours week one but then has fewer hours the next week(s). Having the time evenly spread is messing with resource allocation on the Workload Balancer.
The workload balancer allows a user to group tasks by project which is great. But it needs to go a step further to group those projects by program/campaign.