Table: jira_issue_type - Query Jira Issue Types using SQL
Jira Issue Types are a way to categorize different types of work items in a Jira project. They help in distinguishing different types of tasks, bugs, stories, epics, and more, enabling teams to organize, track, and manage their work efficiently. Each issue type can be customized to suit the specific needs of the project or team.
Table Usage Guide
The jira_issue_type
table provides insights into Jira Issue Types within a project. As a project manager or a team lead, explore issue type details through this table, including their descriptions, names, and avatar URLs. Utilize it to get a comprehensive view of the different issue types in your project, aiding in better project management and task organization.
Examples
Basic info
Explore the different types of issues in your Jira project. This helps you to understand the variety of tasks or problems that your team handles, providing clarity on the project's complexity and scope.
select id, name, description, avatar_idfrom jira_issue_type;
select id, name, description, avatar_idfrom jira_issue_type;
List issue types for a specific project
Determine the types of issues associated with a specific project. This allows for a better understanding of the project's scope and potential challenges.
select id, name, description, avatar_id, scopefrom jira_issue_typewhere scope -> 'project' ->> 'id' = '10000';
select id, name, description, avatar_id, scopefrom jira_issue_typewhere json_extract(json_extract(scope, '$.project'), '$.id') = '10000';
List issue types associated with sub-task creation
Explore the types of issues that are associated with the creation of sub-tasks in Jira. This can help you understand the different categories of problems that typically require the generation of sub-tasks.
select id, name, description, avatar_id, subtaskfrom jira_issue_typewhere subtask;
select id, name, description, avatar_id, subtaskfrom jira_issue_typewhere subtask = 1;
List issue types with hierarchy level 0 (Base)
Explore which issue types in a Jira project are at the base level of the hierarchy. This can be beneficial in understanding the structure of your project and identifying potential areas for reorganization.
select id, name, description, avatar_id, hierarchy_levelfrom jira_issue_typewhere hierarchy_level = '0';
select id, name, description, avatar_id, hierarchy_levelfrom jira_issue_typewhere hierarchy_level = '0';
Schema for jira_issue_type
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
avatar_id | bigint | The ID of the issue type's avatar. | |
description | text | The description of the issue type. | |
entity_id | bigint | Unique ID for next-gen projects. | |
hierarchy_level | bigint | Hierarchy level of the issue type. | |
icon_url | text | The URL of the issue type's avatar. | |
id | text | = | The ID of the issue type. |
login_id | text | =, !=, ~~, ~~*, !~~, !~~* | The unique identifier of the user login. |
name | text | The name of the issue type. | |
scope | jsonb | Details of the next-gen projects the issue type is available in. | |
self | text | The URL of the issue type details. | |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
subtask | boolean | Whether this issue type is used to create subtasks. | |
title | text | Title of the resource. |
Export
This table is available as a standalone Exporter CLI. Steampipe exporters are stand-alone binaries that allow you to extract data using Steampipe plugins without a database.
You can download the tarball for your platform from the Releases page, but it is simplest to install them with the steampipe_export_installer.sh
script:
/bin/sh -c "$(curl -fsSL https://steampipe.io/install/export.sh)" -- jira
You can pass the configuration to the command with the --config
argument:
steampipe_export_jira --config '<your_config>' jira_issue_type