Item statuses

As a Kanban-first project management system, Teamhood puts a lot of attention to work statuses. As well as behaviors related to statuses. In this section we will explain the fundamental principles of item status functionality. Each Board in Teamhood can have a unique set of statuses configured.

Status types

Each status in Teamhood has a type. Status types are used to model workflows and related behaviors. Also, status types can be a good higher level grouping or filtering point in the reports. For example, when you have items in the report from multiple boards and those boards have different sets of statuses. Then you can filter by status type, in case you need to align and for example see only items that are in progress.

• New – should be used to symbolize starting/default status in the workflow.
• In Progress – should be used to symbolize actual work progress.
• Completed – used for storing completed items.

Status structure

Status group

Status groups are visual cues to model larger steps of business process. A good example would be In progress status group, which contains multiple statuses related to actual work, quality assurance and acceptance.

Status

Top level status. It can be set both to parent items and any level of child items.

Sub-status

Sub level status. It can be set only to child items when their parent item is moved to a status which contains sub-statuses. To add sub-statuses, open desired status action menu and choose “insert sub-statuses”.

Child items in status vs sub-status

It’s up to you how you want to model your process. If you go with one level flat process, then you will be able to pick from the same set of statuses to child items and parent items. If you chose to have sub-statuses, then you will have multi level process and more flexibility. Usually high level process steps are different than lower/task level process steps.

When child item is created – it’s status will be determined by the workflow. If flat single level workflow, then child item inherits parent item status. If parent item is in status which has sub-statuses – child item will be created in a first sub-status.

Configuring statuses

• You can configure statuses to have colored icons or fully colored background in Kanban view.
• You can set WIP limits to status or status group level to limit how many items should be there at any given point in time. This is a visual cue and not a hard-enforced rule.
• You can customize the width of status by how many cards it can fit horizontally (affects only Kanban view).

Status automations

When item’s completion is changed to 100% or “Complete” action is clicked, item will get a completion mark as well as will be moved to the first in order status which has type “Completed”. You can have more than one status of type “Completed”. If it has child items, child items will be completed as well.

When a completed item is moved to status which is of New or In progress type – completion mark will be removed and completion % reset to 0.

When a parent item is moved to status which has sub-statuses, it’s child items will be automatically transferred to the first sub-status. If child items are already marked as completed, only completed child items will be put to a first sub-status which has type of “Completed”.

When parent item changes status and that status does not have sub-statuses, child items will remain in their current statuses. Unless child status auto-update setting on workspace level is turned on, in that case, all child items will synchronize their statuses to parent status. Only completed child items will be excluded from auto-update, to avoid “regress” of completion progress.