Item fields

Items are first-class citizens in Teamhood so it is essential to know what properties they have and how to use them. This is an optimized list to cover all available fields.

Default item fields

These are the default fields available for each item in Teamhood:

1. Item ID – a unique reference code for each item. It is composed of a workspace short name and incremental number which starts at 1.
2. Title – item title describing the main idea of the work
3. Description – rich text to provide detailed work specifications.
4. Status – identifies item’s progress in a workflow.
5. Schedule – a combination of start and due dates. Can be used as a single date just for a deadline or a full date range for longer-duration items.
6. Estimate – numeric field which can be configured to be either hours or points. Can be used for work effort estimation or work quantity definition.
7. Duration – numeric field representing time in working days which is necessary to finish the item. If schedule is set, duration will be auto-calculated.
8. Budget – currency field, can be configured to have specific currency suffix/prefix.
9. Tracked Time – time amount field which sums the total tracked time for a given item.
10. Completion – flag which tells if the item is completed or not.
11. Completion % – fractional number to tell how much of the item is completed. Can be set from 0 to 1 symbolizing 0% and 100%.
12. Suspension – flag which tells if the item is suspended.
13. Suspension reason – a field that can be set when suspending to provide a short explanation/reason.
14. Milestone status – a flag that tells if this item is used as a milestone (1-day duration visual cue for project planning).
15. Completed on – if the item is completed it will have the most recent completion timestamp in UTC. Read-only field.
16. Create date – item creation timestamp in UTC. Read-only field.
17. Duration – numeric field which shows item duration in days if the schedule is set. Read-only field.
18. Item age – a field that substracts item creation date from the current date. Read-only field.
19. Creator – contains the full name of a user who has created this item. Read-only field.

Custom item field types

You can add the following custom field types in Teamhood:

1. Text – a short form text field. To add important information.
2. Number – a field to add in numerical values. For example, count the number of resources used for the task.
3. Checkbox – a clickable checkbox for yes/no type answers.
4. Select – a field that allows to define mutiple values and select one of them.
5. Multi select – a field that allows to define multiple values and select as many as needed. (paid feature)
6. URL – a field that allows to add a clickable link. This link can be displayed on Kanban cards.
7. Formula – a field to define custom values by calculating arithmetic operations. (paid feature)
8. Email – a field for adding a clickable email address.
9. Date – a field that allows to enter a date. Can be used for for single date input. (paid feature)
10. User – a field that allows you to choose from available workspace members. (paid feature)
11. Checkbox (timestamped) – a field for capturing date when the checkbox was clicked. (paid feature)

Field descriptions

You can add a description to any custom field to explain how it should be filled in. The description appears when someone hovers over the field title.

This is the cheapest way to keep data consistent across a team — a one-line note like “use the client’s PO number, not ours” prevents most of the mess that otherwise builds up in a shared field.

Read-only fields

Workspace Admins can mark selected fields as read-only. This applies to custom fields as well as Budget and Estimation.

When a field is read-only, only workspace Admins can change its value. Everyone else can see the field but not edit it — which is what you want for figures owned by finance or a project lead, where visibility is helpful but edits should be controlled. See roles and access rights for the full permission model.

Baseline fields

Baseline fields hold the originally planned values for an item, so you can compare the plan against what actually happened. Combined with formula fields, they let you calculate the difference between planned and actual figures and track deviation over the life of a project.

Saving and reverting baselines is covered on the Gantt page.

How aggregated values are displayed

For tracker fields, you can configure how a parent item’s summed-up value is presented. In Item field settings, the sum-up format dropdown offers:

• Auto — shows the item’s own value, or the sum of its child items.
• Total — the item’s own value plus the child sum.
• Split — the item’s own value and the total, shown separately.

Choosing the right format matters when parents carry their own work as well as children — Split is usually the clearest in that case. Aggregated values are also returned by the Open API.

Private fields

In Teamhood you can hide certain fields from certain users. Go to Workspace settings -> Item fields. Mark field as private and give access only to those who should see it.

If user does not have access to the field, user will not be able to see:

1. Field data in any view and item details
2. Changelogs related to that field
3. Notifications related to that field
4. Access field itself for modification

Hiding fields only in certain boards

There is another option when you are fine with everybody seeing data of that field, but you just want to hide it to reduce cluttering in certain boards. Go to Workspace settings -> Item fields. Select the desired field and untick the boards where you want to hide it. This is helpful when working in multi-board workspaces, where each board can have a different set of fields required.