User guide · Projects
Project settings
A project's Settings are open to its Lead and Owner. The General tab saves with one button; every other tab saves each change as you make it.
General
| Section | Settings |
|---|---|
| Identity | Name, description, key and status. Set status to archived to take a project out of the way without losing anything. |
| Client and contract | Account, programme and delivery model. Portfolio views group by account and programme and judge the project by its model. Changing the delivery model needs a Delivery manager, Workspace manager or administrator. |
| People and access | The Lead its questions go to, its Visibility, and its Workstreams, shown read only. Membership is on the Team page. |
Workflow & board
- Workflow: the statuses work moves through and the moves allowed between them, on a canvas. The project has its own copy, so changes reach this project only; the whole workflow saves in one go.
- Board: which column each status lands in, each column's WIP limit, and new statuses.
Hierarchy
The work item types the project uses, each one's tier and kind of work. A parent must be on a strictly higher tier than its child. Moving a type to another tier can convert estimates between points and hours, with a preview first. When the project's types differ from the agreed set, the tab lists what differs: its portfolio figures won't line up until fixed.
Fields
Custom fields are extra fields this project's work items carry. Choose which screens a field appears on when you create it. Its key is fixed, so renaming never breaks a screen.
Screens
A screen decides which fields a form shows, in which pane (Main, Planning or Details), in what order, and which are required. Each type has one per operation: Create, Edit and View. Drag fields to lay it out, or use the move buttons from the keyboard. A screen can hide, reorder or require a field, never add one the type doesn't allow.
Labels
Labels are the project's free-form tags. From a label's menu: Rename or recolour everywhere at once; Archive to take it out of pickers without touching items; Merge one into another; Delete one nothing uses.
Policies
- Points to hours: whether story points become hours for resource planning, and at what rate.
- Billable: whether a new time log on this project starts out billable. Each log can still be switched.
Integrations
Azure DevOps connects the project to an Azure DevOps organisation and imports its work items: hierarchy, area paths, iterations, states, assignees, estimates, tags and dates.
- Credentials are tested before they are saved, and stored encrypted.
- Assignees and creators with no account get one, with a resource profile, and become members. They get no login until someone sends one from People.
- Re-importing updates what the last import created instead of duplicating it. Azure DevOps' Resolved lands in the first review status.
Danger zone
Delete project removes its work items, sprints and board for good. Only the project's owner or an administrator can do it. Archive it from General if you only want it out of the way.