Work item type
A work item type is the shape of a piece of work: task, bug, story, epic or request. Each type owns its fields. A bug asks for severity and steps to reproduce; a story asks for acceptance criteria; a request records the channel and who asked.
The hierarchy is built in: an epic contains stories, a story contains tasks. Custom fields extend any type. This is the single carrier for fields, workflow behaviour and notifications, instead of a stack of schemes.
Video work still uses tasks. Software and QA use bugs and stories. Support uses requests. The engine does not care which type sits on which stage.
Perguntas frequentes
- Can I add a sixth type?
- Workspaces start with those five. Custom fields extend them. A marketplace of types is not here.
- Does a type own its workflow?
- The project's workflow is the path. The type owns the fields the item carries along that path.
- Is this Jira's issue type plus schemes?
- No. Tasked uses one carrier on purpose. Schemes are listed as something this product will not build.