Feature Requests

At Teamhood we want to give our end users a way to create their own version of Teamhood on top of their project data. This is where Teamhood AI comes in. What to expect now Currently the biggest flexibility chokepoint is different reporting options. Thus, we have decided to start with read only data part which is also less risky. Currently, Teamhood AI can retrieve and represent data from all your workspaces into a well known spreadsheet format. You can add charts or export as .csv and transfer that data to other systems. What to expect later Generate more complex UI's such as timelines and Gantt charts Ability to edit data Retrieve data from other systems

We would like to see the original plan for completing the task (from - to) and the actual plan. Because if a task is performed ahead of time and the plan of planned tasks is rescheduled, the original plan is not visible. You should see Plan - Change required, Baseline threshold Actual (after recalculation) - already visible

Users want to keep their files in sharepoint without uploading to Teamhood, but still be able to link those files in Teamhood via attachment action.

When filtering by a custom field that is a string text, it would be nice to add in "Does Not Contain" or "Does Not Equal". I use it for our planned releases, and it would be nice to filter some out by having the does not contain or does not equal option.

For the system to automatically postpone the start dates of dependent tasks until the previous task is completed. We have noticed that if, for example, the contractor's role is late for a task, the project engineer is automatically late for the task, etc., even though he even had a chance to start the task yet, i.e. the time limit hasn't started to run. In this case, we get a whole batch of late tasks, when in fact one task is late because the other tasks after it could not even have been started, resulting in distorted reporting and inaccurate information. It should therefore be made so that if there is a delay in the completion of a task, the execution plan is recalculated by + 1 d each day until the preceding task is completed.

When a column is collapsed on the Kanban board, the summary of items floats to the vertical centre of the column. On a busy board, this is often off-screen. It would be much more useful if it floated to the top of the column

Hello Teamhood Team, I would like to request a feature that allows limiting the number of tasks displayed per column (status) on a board. Currently, if a status (e.g., “To Do”) contains a very large number of tasks (for example, 100+), all of them are shown at once. This can make the board difficult to navigate and visually overwhelming. The improvement I suggest: • Allow users to define a maximum number of tasks visible per column (e.g., only the first 10 tasks). • Add a “Show more” button at the bottom of the column to expand and display the remaining tasks. This feature would help keep boards clean, easier to read, and more efficient, especially when working with statuses that accumulate many tasks. Thank you for considering this enhancement! Best regards, Salih Can

Different teams use different points scales. Some examples include: Linear: 1, 2, 3, 4, 5, 6, ... Fibonacci: 1, 2, 3, 5, 8, ... Exponential: 1, 2, 4, 8, 16, ... T-Shirt: S, M, L, XL, ... It would be great if Teamhood could support more than just the current fixed range.

We can @ people in comments; can we please @ them in Task descriptions?

The ability to move the location of a task in response to external events (such as Github PR events) Some use cases: moving a task from one column to the next on a Kanban board moving a task from the Backlog board to the Backlog of the Kanban board once certain criteria are met