What are default [System] issue types?

Each Jira product comes with a set of issue types to suit the needs of your projects and teams. Each IT service management work category (Service requests, Incidents, Problems, Changes, and Post-incident reviews) has a default issue type that is set up with best practice workflows and fields for each of these categories. You’ll see these issue types in your service project with [System] at the start of their name.

Default issue type fields

• [System] Service request fields: Urgency, Impact, Pending reason, Product categorization, and Operational categorization.
  
  

• [System] Incident fields: Affected services, Affected hardware, Urgency, Impact, Severity, Pending reason, Source, Product categorization, Responders, and Operational categorization.
  
  

• [System] Problem fields: Affected services, Affected hardware, Investigation reason, Urgency, Impact, Root cause, Workaround, Pending reason, Source, Product categorization, and Operation categorization.
  
  

• [System] Change fields: Affected Services, Change type, Impact, Urgency, Change risk, Change reason, Implementation plan, Backout plan, Test plan, Planned start date, Planned end date, Change start date, Change completion date, Approver groups.
  
  

• [System] Post-incident review fields: Affected services, Affected hardware, Urgency, Impact, Severity, Pending reason, Source, Product categorization, Responders, and Operational categorization.

Learn how to add all default fields to an issue type.

A Jira Service Management administrator can add and delete issue types from a service project to represent different types of work that agents do. Each Issue type maps to a single specific workflow, but can access any of the fields available in your service project.