Feature Requests

Using an if-clause in a custom field with a formula works great. We use it to calculate (quote value * probability %). This gives us the total funnel value at the bottom of the row. When we added an if-clause to return €0 when probability is below a certain %, this is also reflected correctly in the custom field. Only, the row total does not take the if-clause into account.

often same resource get assigned ugent/high priority task, It would be nice that lower priority task get delayed to reflect that resource will be working on new higher priority tasks (like MS project does)

Hi Team, A nice feature to have would be the ability to show items based on custom date information, instead of solely start/due date. The use case for our team for example is we use start/due date for beginning and end of a project, but the execution of the project can be in a smaller range between the start/due date. Also only showing on start/due date means the calendar quickly loses it's overview because it's possible to have many overlapping projects due to bigger start/due date ranges. Thank you in advance! Kind regards, Michaël

Importing is actually quite difficult without a template, the only solution is getting a free trial exporting an existing list, interrogating the CSV file, and creating your own template to use. A template and instructions would be beneficial.

There are many times where my projects would have benefitted from being able to lock down sections of baseline as the planning and stakeholder / org. alignment went along. Instead of just a single Gantt overall baseline save, I request to be able to save / update baseline on individual rows. I would also like to see the ability to save multiple baselines and be able to recall them again.

Currently a large portion of the worlds coorporations are running Microsoft products. Because of this many are using Teams as default meeting tool. With the arrival of AI solutions Teams meetings are getting closer and closer to being good at writing automated meeting minutes, including generating task lists. The current MS setup is that: Teams meeting facilitator AI generates Loop page for meeting minutes and notes > If tasks are identified these are created as a Loop component Task list > A Loop component task list generates a Planner Basic (light) plan which has the tasks. This allows for tasks to be assigned easily to meeting attendees, and for the attendees to manage their tasks in MS Planner / To Do. Loop components sync across all locations they are used. Being able to easily sync the Planner tasks with a Teamhood board / gantt chart, would remove the manual workflow of: MS Planner > Export excel > Convert to CSV > Import to Azure DevOps > Sync to Teamhood.

When a workspace is configured to accept emails from any sender and automatically create items from incoming emails, Guest Collaborator users currently cannot create items by sending emails from their own email addresses. This creates an inconsistency in the permission model: The workspace explicitly allows item creation through the email-in channel. External users and non-workspace members can successfully create items via email. Workspace admins can create items via email. However, a user who exists in the workspace as a Guest Collaborator is blocked from creating the same item through the same email channel. Business Scenario Many organisations use Guest Collaborators as customers, partners, or external stakeholders. A common workflow is: A customer sends an issue, request, or feedback via email. Teamhood automatically creates an item in the board. Workflows assign the item to the appropriate team members. The customer is assigned as a watcher or assignee and can track progress inside Teamhood. Currently, if the customer is registered as a Guest Collaborator, the item creation fails, even though the same email would succeed if sent from a non-registered external email address. Suggested Behaviour When "Accept emails from any sender" (or equivalent email intake setting) is enabled, Guest Collaborator users should be allowed to create items through the email-in functionality, even if they do not have permission to create items directly in the UI. This would: Enable customer-facing ticketing workflows. Remove the need for workarounds using intermediary email accounts. Keep UI permissions unchanged. Preserve the intended licensing model while improving automation and user experience. Expected Outcome Guest Collaborators remain restricted from manually creating items in Teamhood boards, but they can generate items through the configured email-in integration when the workspace owner has explicitly enabled email-based item creation. Impact: Medium to High. This would significantly improve customer support, service desk, and stakeholder collaboration scenarios without expanding Guest Collaborator permissions in the application UI.

Currently templates don't retain their waiting on/blocked/synced task information. I understand it's a very limited use case for blocked/waiting on items, but templates retaining sync items would allow you to quickly assign tasks to different teams using different boards for repetitive items. Thank you in advance. Kr, Michaël

Proposal to be able to share a public view of a Gantt chart. Use Case would be for publishing to a Project Portal Sharepoint site. This would easily allow other roles in the company to get a feel for / understanding of the schedule of a specific project. I don't know how it could be made though.

Make it so that Item types can be defined as being local only. I do not know if this would be done easiest by have a flag for each item for whether they should be synced or local only, or if an actual Item library could be made for each Teamhood board. My thoughts is that for e.g. developers working in Azure DevOps system, many project admin deliverables and such is irrelevant and would simply clutter the ADO system. Therefore the Project Manager could keep such items locally in the Teamhood workspace / gantt chart. Furthermore this would also solve the issue of Milestones and Gates being able to be Teamhood exclusive items, as then you could simply flag any item in Teamhood to be local only, and then flag it to be a Milestone, etc.