Types
Settings → Types, or /p/{projectId}/settings/types.
A type is an option of one select, such as Bug or Story. It is not a thing of its own: the project names one select as its Type, and each option of that select is a type. A property can then show only on the types it applies to — Severity on a Bug, Acceptance criteria on a Story.
This page is the Properties page read type first. It stores which select is the Type. Everything else on it is each property’s Shown when rule, and what it starts as.
Pick the select owner and admins
Section titled “Pick the select ”With no Type, the page says what a type is and offers Types come from, a list of the project’s selects. Pick one. Pick No select to stop. A member reads the page and cannot pick.
Open a type
Section titled “Open a type”The page lists the types, which are the options of the select in their order and colours. Press one to see what a task of that type shows:
| Group | What is in it |
|---|---|
| Every type | The properties with no rule. Each type shows them. |
| This type | The properties whose rule names the Type and this type. A property that is on other types too says also on Bug, Story. |
| On other types | The properties whose rule names the Type, but not this type. |
| Shown by another select | The properties whose rule names a different select. They show their rule in words, such as Shown when Area is UI. Change them on the Properties page. |
Change what a type shows owner and admins
Section titled “Change what a type shows ”- Add to Bug puts this type into the rule of a property that is on other types. It hides nothing, so it saves at once.
- Only on Bug limits a property on every type to this type. The other types stop showing it.
- Take off Bug takes this type out of the rule. When this is the only type the property is on, the row offers nothing and points to the Properties page, which can make it show on every type.
A change that hides a property drops its values from the tasks that stop showing it. Before it writes, the row asks with the count: 12 tasks lose their Severity. This is the same question, and the same write, as on the Properties page.
Add type, under the list, adds an option to the Type select.
Say what a type starts with owner and admins
Section titled “Say what a type starts with ”Each property a type shows that can carry a value — a select, a multi-select, a checkbox, a number or text — has Starts as under it. Pick a value there, and every new task of that type starts with it: a Bug starts with Severity Minor. A person never has one.
The server writes it on every create, from the board, a list or an agent, for each property the create did not set. The composer says it before you press Enter: starts with Severity Minor. On a board grouped by Type the column names the type; elsewhere a filter that sets the type does. A task that changes its type later keeps its values. Delete the type or the value, and the default goes with it.