Types, fields, views and hierarchy
Teamhood is built from four ideas: types, fields, views and hierarchy.
Types — what an item is
Section titled “Types — what an item is”Every item has a type. A new organization starts with three.
| Type | What it is for |
|---|---|
| Project | A body of work with a start and a finish |
| Task | A unit of work, and the default child of everything |
| Issue | A problem to resolve, shaped like a Task, in its own colour |
A type decides four things: the colour an item shows and the fields it carries. It also decides what may live inside it and what happens when you open it.
A Project opens to show its children. A Task or an Issue opens its own detail panel. Ctrl+click opens the other one instead.
You can add your own types in Settings.
Fields — what an item knows
Section titled “Fields — what an item knows”Fields hold the values on an item, such as Status, Start, Finish, Assignees, Estimate (h), Tags and Tracked Time. Each field is scoped to the types it applies to.
- Status drives the board columns. A status the type does not allow is refused.
- Start and Finish drive Gantt bars and Schedule bars.
- Estimate (h) and Assignees are what the Workload view reads to show who is booked.
Views — how you look at items
Section titled “Views — how you look at items”A view is a saved way of looking at your items, never a separate copy of them. Change an item in one view and every other view already agrees.
See Create your first view for adding your own view.
Hierarchy — how items nest
Section titled “Hierarchy — how items nest”Any item can live inside another item.
- Progress rolls up. Complete every child and the parent completes itself.
- Context rolls down. The Project field on a task resolves the nearest project above the task. Picking a different project in that cell moves the item.
- Deleting rolls down too. Deleting an item deletes everything inside it.