Feature Requests

Please search first before posting to help others find and vote for your idea!
Vast improvements needed to resource planning
We need users to be able to set their regular schedules on a two-week cycle that corresponds to our pay cycle. We have half our workforce on a schedules where they work 4 9-hr days one week, then 4 9-hr days + 1 8-hr day the following week. A built in time-off workflow would be helpful so it can incorporate vacation days in a person's capacity. The relationship between time estimates and time entry makes no sense. If enabled, time estimates should not be able to be less than time entered. If time entered is allow to exceed it, then it means that the workload view and any discussions on resource planning, are underestimating effort. Lack of a "work remaining" field is silly. Although we can create a custom calculated field to do the math, it is not really effective. For one thing, problem #3 means work remaining can result in a negative number. Even if you account for that in the field's formula, custom fields cannot be made to roll up so the discrepancies caused by problem #3 makes the calculation on parent tasks inaccurate because it has to rely on the total time estimate and the total time entered so the 100 hours left of work to do on subtask A gets wiped out by the 100 hours on subtask B that were entered with no time estimate. The options in workload views to include subtasks or exclude subtasks and include roll ups should generally result in very similar totals for a given employee for a given time period. But they are drastically different. I've worked with Brain and a lot of trial and error to get them better aligned and I cannot. Even if I make sure the person is assigned not only to the subtasks where the time estimates live, but also all parent tasks in the chain, it still doesn't keep the subtask hours in the proper time period but just seems to spread it evenly over the entire duration of the project which could is typically 9-18 months. So the " include subtasks" view creates a long list of subtasks making it difficult to see the global picture, or the "exclude subtasks" and "include rollups" combination vastly underestimates the ebbs and flow of assigned work. So does not allow us to see who might be available small discreet tasks in a given month. The link between planner and Outlook is deeply flawed so that recurring and single occurrence all-day events do not show up on the correct date. We could find a way to compensate for the lack of #2 with this integration and potentially some sort of automation, but because all-day events like days out of office do not show up correctly. This flaw also makes using Brain to assist with time entries less effective.
1
·
Time Tracking &…
Load More
→