An issue type is the subject in project collaboration. For example, a requirement and a task can both be referred to as an issue type. You can add an issue type called Maintenance, modify its type icon, and then specify its fields and workflows in the project. Issue types can be categorized as team-level (or global) and project-level types. You need to define the global issue types first, and then apply them to projects.
The global issue type list shows all the issue types in a team. Issue types are divided into built-in types and custom types. The icon and name of a built-in type (such as epic, requirement, task, bug, user story, and sub-issue) cannot be changed.
User Story is a new built-in type. As the smallest unit of work in an agile framework, it describes the value brought by software to users.
Note:
When creating a custom issue type, you can select an icon for it, and add a description. The custom issue type can be copied, and a replica of it is created automatically.
Custom requirements and custom tasks can be created for custom issue types, which can be manually deleted when they are disassociated with the project.
Fields are used to describe the current status, due date, assignee, priority, and other information of the issue. Basic field information (such as title, description, attachment, and associated resources) is not included. All the fields on the field configuration page are shown on the issue details page and can be used in search and filters. For more information, see Custom Issue Fields.
Custom workflows can be designed for both agile and classic modes to meet unique demands of different teams. More importantly, global workflow statuses allow you to define consistent statuses and improve collaboration efficiency across projects and departments. See Custom Workflows for details.
Yes
No
Was this page helpful?