Table: jira_component - Query Jira Components using SQL

A Jira Component is a subsection of a project. They are used to group issues within a project into smaller parts. You can set a default assignee for a component, which will override the project's default assignee.

Table Usage Guide

The jira_component table provides insights into the components within a Jira project. As a Project Manager or Developer, explore component-specific details through this table, including component name, description, lead details, and project keys. Utilize it to manage and organize issues within a project, making project management more efficient and streamlined.

Examples

Basic info

Explore which components of a project have the most issues, helping to identify areas that may need additional resources or attention.

select
  id,
  name,
  project,
  issue_count
from
  jira_component;

select
  id,
  name,
  project,
  issue_count
from
  jira_component;

List components having issues

Determine the areas in which components are experiencing issues, allowing you to assess and address problem areas within your projects effectively.

select
  id,
  name,
  project,
  issue_count
from
  jira_component
where
  issue_count > 0;

select
  id,
  name,
  project,
  issue_count
from
  jira_component
where
  issue_count > 0;

List components with no leads

Determine the areas in your project where components lack assigned leads. This can help in identifying potential bottlenecks and ensuring responsibilities are properly delegated.

select
  id,
  name,
  project,
  issue_count,
  lead_display_name
from
  jira_component
where
  lead_display_name = '';

select
  id,
  name,
  project,
  issue_count,
  lead_display_name
from
  jira_component
where
  lead_display_name = '';

Schema for jira_component

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
assignee_account_id	text		The account id of the user associated with assigneeType, if any.
assignee_display_name	text		The display name of the user associated with assigneeType, if any.
assignee_type	text		The nominal user type used to determine the assignee for issues created with this component.
description	text		The description for the component.
id	text	=	The unique identifier for the component.
is_assignee_type_valid	boolean		Whether a user is associated with assigneeType.
issue_count	bigint		The count of issues for the component.
lead_account_id	text		The account id for the component's lead user.
lead_display_name	text		The display name for the component's lead user.
login_id	text	=, !=, ~~, ~~, !~~, !~~	The unique identifier of the user login.
name	text		The name for the component.
project	text		The key of the project to which the component is assigned.
project_id	bigint		The ID of the project the component belongs to.
real_assignee_account_id	text		The account id of the user assigned to issues created with this component, when assigneeType does not identify a valid assignee.
real_assignee_display_name	text		The display name of the user assigned to issues created with this component, when assigneeType does not identify a valid assignee.
real_assignee_type	text		The type of the assignee that is assigned to issues created with this component, when an assignee cannot be set from the assigneeType.
self	text		The URL for this count of the issues contained in the component.
sp_connection_name	text	=, !=, ~~, ~~, !~~, !~~	Steampipe connection name.
sp_ctx	jsonb		Steampipe context in JSON form.
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_component