Field description - Type
The issue Type tells you what kind of issue it is. Type names should be descriptive of what you do with that kind of issue.
Issue types can be configured to behave quite differently from each other
Default name: Type
Terminology variations: None by default, but several places in the system mention "Issue Type", and in that case it is depending on the terminology setting for "Issue", resulting in Task Type, Item Type, Case Type etc.
In-Use: Always. This field is always used and cannot be removed from the issue field configuration.
Mandatory: Yes. This field must be set on an issue.
Data type: An issue type. You can create and edit Issue types in General > Settings > Issue configuration > Issue types.
Access restrictions: No access when creating an issue (as the type is already determined from your "new issue" selection). Editing: Read/Write by default for internal users, and No access for support users by default.
Relationships/Dependencies: Many settings are dependent on the issue type.
Issue field configuration: You can set issue fields to be shown only for some issue types
Project > Settings > General > Statuses: A Status could be set to be shown only for some issue types
Affected by these settings:
General > Settings > Issue configuration > Issue types:
Here you can define the names, appearance (icon, background color) of issue Types, as well as some flags (Is Meeting, is Milestone, is Default). Be sure to set at least one issue type as the default issue type.
The issue types available by default in a new account are: Bug, Task, Feature Request, Support issue, Meeting. These should cover a lot of cases and get you started.
Project > Settings > General > Issue types:
Here, you can select which issue types that should be used on the project. You can also determine which User groups are allowed to create an issue with a specific Issue type.
Use cases: Use different issue types for different kind of work/tasks, and tailor the available fields and the issue behaviour to each issue type.