Jira application can be used to break several workpieces into issues. Subsequently, these issues can be represented through tasks, buds, subtasks, feature requests, epic, and other pieces of work. Every default Jira software comes with associated issue types which can be chosen based on suitability for a project or team.
Subsequently, Jira training can be given to the members to handle issue types. An issue type is how different issues are classified in a Jira project. There can be standard types that usually come with Jira, and there can be additional custom types of issues. Let us discuss the default Jira issue types that usually come with Jira software in greater detail.
There are three different types of Jira issues that you can encounter with Jira software. There are categorized into the following:
Let us discuss each one of them in greater detail.
Core issue types mostly deal with business projects and can be easily classified into two subcategories, namely task and subtask.
A task is a type of work that is due for completion or meant to be done to achieve the goals determined by a team. A task is mostly generic.
A subtask can belong to an issue wherein all the tasks that collectively fall under the category of a logged issue will be known as a subtask. So it is a smaller task within a larger piece of work that will be needed to complete the latter. A subtask may assign parts of the larger work to separate team members.
The issue type Jira involved in this case is software projects. They are further subdivided into different categories, which are enlisted below.
A bug is a type of problem that can impair the functionality of a product or a service. It is often used to track problems identify errors, omissions, defects, or things that need fixing.
An epic is a large piece of work under which many different issues fall. It is a large user story that can be broken down into many smaller stories but completing an epic might take a long time. Epics are usually converted into user stories, and then these user stories are converted into tasks that an Agile team usually works upon.
Epics are broader in scope and lack details but can be split into smaller multiple stories, giving the Agile team a base to work upon. In the hierarchy of work, an epic usually falls in the top tier.
A story is a type of functionality request expressed from a user's perspective. Usually, a story is used by a software development team to make sense of the requirements, features, and enhancements. A story may be expressed as a list of tasks that need to be completed within a project. It is capable of defining the high-level design of project requirements.
Usually, a story can also be used to define the short and simple descriptions of the whole project. Anyone can write user stories, but the product owner of a company owns them. Stories are written in fairly simple language to easily help customers understand the final product.
Other than some of the default issue types in Jira, the following issue types can also be encountered.
This issue type is used to request a change in the current profile. It may be highly relevant during the rollout of new technologies and solutions.
This issue type can be understood through Jira certification and reports the root cause of many incidents. It may also be relevant in tracking any underlying cause of incidents.
This issue type is used for requesting assistance from a service desk either through internal or external sources. It is a general request made from a user for a product or service.
Service Request With Approval
This type of issue is used for requesting help which can be availed only through approval from a manager or board.
An incident is a type of issue used to report an incident such as a service IT outage.
Such issue type is used to request help for a problem that relates to IT.
This type of issue is used when a request for the addition of a feature or a new feature, or a new software capability is required.
This type of issue can be understood through Jira training online and is widely used for requesting help for different types of customer support issues.
Besides these predetermined issue types, it is possible to have additional custom issue types in the selection list of a project. If so, they will be added by the Jira administrator, either by using a third-party app or by using additional Jira functions.
So, for example, a legal Jira project may have several additional custom issue types, such as an agreement or a contract. Similarly, a marketing Jira project may have an issue type: creative, campaign, or design. Although custom issue types can be expected in every field, a Jira administrator's job is to keep the list of issue types as short as possible.
During Jira certification training, you will learn about issue type schemes that help determine which issue types shall be available for a given project or a set of projects. Jira administrators can juggle multiple issue types, depending on where they need to be used. The above list of issue types is standard but not exhaustive, in the sense that there is scope for several other custom issue types, which can be added, depending on the needs of the project.
>4.5 ratings in Google