Issue Types

On this page:

Issue types and their usage

Power Admin for Jira allows you to find any issue type in your configuration and get a full report about its dependent issue type schemes, issue type screen schemes, workflows, workflow schemes, agile boards, and filters.
You can view where and understand how each issue type is used. Power Admin also shows all the projects where the issue type is configured for a project and all the issues of this type.

Issue types → Projects relation

The usage in projects is determined by the usage of issue types in issue type schemes, issue type screen schemes, workflows, and workflow schemes.

Power Admin detects if an issue type’s dependent issue type schemes, issue type screen schemes, workflows, and workflow schemes are associated with projects. In this case, Power Admin will show that the issue type is configured in these projects (Projects counter in the Summary section).

For example, say you have an issue type screen scheme used in a project. If an issue type is associated with a screen scheme in that issue type screen scheme, Power Admin will detect that the issue type is part of that project’s configuration.

Find issue types

To find an issue type:

  1. On Power Admin's Landing page, select Issue Type from the drop-down, type a name or id, and start your search.

  2. On the Search results page, click on the name of an issue type. You can filter further the issue types by usage in projects (use the Projects filter on the Search page).

  3. Then, the issue type’s profile page appears.

Search results

The page with search results shows the following information for each issue type:

  • Name and id of the issue type - You can search for an issue type by its name or id.

  • Projects - shows the count of the projects where the issue type is part of the project configuration of its dependent configuration elements. When you click on the project count lozenge, you will see a list of all the projects.

  • Issues - shows the count of issues of this type that exist.

Issue type's profile page

Using the profile page, you could view all the details about an issue type and its usage.

How does Power Admin track the issue type usage?

Power Admin finds all projects where the issue type is present in the project configuration. The usage information also includes the issues that have values for this issue type.

Power Admin collects all the issue type schemes, issue type screen schemes, workflows, workflow schemes, agile boards, and filters that use the issue type. We go through the JQL entries of agile boards, filters, and dashboards and look for references to the issue type.

Learn more details about how Power Admin tracks the usage information of issue types.

Usage Information

An issue type's usage information is presented in the Summary and Details sections on its profile page.

Summary

The Summary section shows:

  • Count of the projects where the issue type is configured. You can click on the count to view a list of the projects.

  • Count of the issues of that type. When you click on the issue count, you will be redirected to the Issue Navigator listing the issues.

  • Count of dependent issue type schemes, issue type screen schemes, workflows, workflow schemes, agile boards, and filters.

Details

The profile page's Details section shows the issue type schemes, issue type screen schemes, workflows, workflow schemes, agile boards, and filters that depend on the issue type.

Agile boards do not have a profile page in Power Admin.

Actions

The following actions are available for issue types:

  • Rename - You can click on the name of an issue type to rename it. Rename is a safe activity, which means that the name of the issue type will be updated in all dependent configuration elements referring to it by name. Renaming the issue type will update all JQL queries within filters and agile boards with the new name.

  • Delete - delete action is not allowed if there are issues of that type.

  • Export - exports an issue types usage information in CVS.

Locations

Location details are not available for for the relation between issue types and their dependent configuration elements.