Feature Requests

Please search first before posting to help others find and vote for your idea!
Expose per-assignee time estimates and "Modify work by day" data via API
We use the Workload Capacity API (get_workload_capacity) to power a department-level dashboard that mirrors the Workload view. The API covers nearly everything correctly: subtasks, spanning tasks, closed tasks, group-assigned tasks, and standard time estimate spreading. However, two Workload view features produce values that are invisible to the API, causing discrepancies that undermine trust in API-sourced tooling. Feature 1: Per-assignee time estimates Business+ allows setting individual time estimates per assignee on a multi-assignee task (e.g. Daniel 4h, Jonathan 4h, Ezgi 0h on a 10h task). The Workload view renders these correctly, but neither the Task API nor the Workload Capacity API exposes the per-assignee breakdown. The Task API returns only the total timeEstimate. The Workload Capacity API sometimes applies the split internally but not consistently, and the per-assignee values are never returned in the response. Requested: Add a time_estimates_per_assignee field to the Task API response (or a dedicated endpoint) that returns each assignee's individual estimate when set. Feature 2: "Modify work by day" allocations The Workload view allows manually redistributing a task's hours across specific days (e.g. moving a 10h task from even M-F spreading to 0-0-0-5-5). The API uses the standard spreading algorithm and does not reflect these manual daily adjustments. Requested: Expose the daily hour allocations set via "Modify work by day" in the Workload Capacity API response, or as a per-task field. Impact: Any team building dashboards, reports, or automations on top of the Workload view data hits this wall. The workaround (telling users "the numbers are close but not exact") erodes adoption. These two endpoints would make the API a true mirror of the Workload view.
0
·
Time Tracking &…
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
→