Where types come from
You define types once for the instance. A project then offers them in one of two ways:
When a project type and an instance type have the same name, members see the project type only. A project cannot hide an instance type. If a team must not use a type, give it a project from a template that leaves the type out.
Create a work item type
1
Open Work Item Types
Open System Settings → Content & Organization → Work Item Types and click New Work Item Type.
2
Fill in the panel
3
Save
Click Save. You see Work item type created and the type appears in the list.
Give a type its own fields
Link field collections to a type on the collection, not on the type:1
Open the collection
Open System Settings → Content & Organization → Field Collections, select the collection and click Edit.
2
Link the type
Under Work Item Types, pick the type in Link work item type…. The Collections column on the Work Item Types page shows the link.
Give a type its own workflow
Each project, or each project template, maps work item types to workflows. A type without a mapping uses the project’s default workflow. See Workflows in a project.Types in project settings
A project’s Settings → Work Item Types lists the types the project offers. Types from the instance carry the badge Global. Types without the badge belong to the project, for example the copies a project keeps when it is detached from its template. You can delete only types that belong to the project. If the project is linked to a template, the section is read-only and says Work item types are managed by the linked template.Delete a type
Types that come with Collabase as system types cannot be deleted.
Related pages
Custom fields
Fields and the collections you link to types.
Workflows
The statuses a type’s work items move through.