Feature Requests

Problem: Users in our organization often log time on items after they've already been moved to a "Done/Completed" status. This distorts sprint metrics, reduces data accuracy, and makes audit trails unreliable. Today there's no way to prevent or limit this in Teamhood. Proposed solution: Add two new settings to the Tracker field configuration (Workspace → Item fields → Tracker): Allow time logging on completed items (toggle on/off) — when off, time entries are blocked on items in a "Done/Completed" status. Backdating limit (number of days) — defines how far back users can register time entries (e.g. 7 days). A value of 0 / "unlimited" preserves current behavior. Keeping these as Tracker-field-level settings lets admins enforce stricter time-tracking discipline where needed, without imposing a single rule on all Teamhood customers.

Currently unable to apply item templates to Items created using the API

The workload report is very helpful. Anyway, when there is an overallocation it'is hard to pick which activity to postpone because the bar shows the total effort. It would be nice to have the daily effort for that person, as well. In this way, you immediately know the effect of postponing an activity on the daily workload.

It's easy to copy a link to an item. There is no way to copy a link to a row. I sometimes want to send a row to a team member and instruct them to update the status of every item in a row.

Be able to see comments on tickets from the API and add/remove comments via the API

It would be cool to upload different types of files into Pages, for example: .pdf .docx .xlsx ...etc Thank you for great product!

It would be helpful to be able to create intake forms within Teamhood. This will allow onboarding process of all new work/projects as a one stop solution. This would also allow designing a form with necessary columns (e.g., Project Name, Description, Date), clicking Forms > Create Form, and customizing fields. These forms allow stakeholders to submit data without needing direct board access. Data is saved directly into the form, which can then trigger automated workflows for approvals.

Rows operate like folders, but they do not allow for the assignment of tags, custom fields, assignees, or any additional information. Furthermore, there is currently no option to move Rows between Boards.