Table: jira_workflow - Query Jira Workflows using SQL
Jira Workflows is a feature within Atlassian's Jira software that enables teams to manage and track the lifecycle of tasks and issues. It provides a visual representation of the process an issue goes through from creation to completion, allowing teams to customize and control how their work flows. Jira Workflows helps in determining the steps an issue needs to go through to reach resolution, setting permissions for who can move issues between steps, and automating these transitions.
Table Usage Guide
The jira_workflow
table provides a detailed view of Jira Workflows within a Jira software instance. As a project manager or a team lead, leverage this table to gain insights into the steps, transitions, and status categories of each workflow. Utilize it to manage and optimize your team's work process, understand the lifecycle of tasks, and identify bottlenecks in your project's workflow.
Examples
Basic info
Analyze the settings to understand the default workflows in your Jira system, enabling you to better manage your project processes and prioritize tasks. This is particularly useful for project managers who need to assess the elements within their workflows and identify areas for improvement or customization.
select name, entity_id, description, is_defaultfrom jira_workflow;
select name, entity_id, description, is_defaultfrom jira_workflow;
List workflows that are not default
Uncover the details of workflows in Jira that have been customized and are not set as default. This can be beneficial for administrators to understand the unique workflows in their system and make necessary adjustments or improvements.
select name, entity_id, description, is_defaultfrom jira_workflowwhere not is_default;
select name, entity_id, description, is_defaultfrom jira_workflowwhere is_default = 0;
List workflows that are not associated with entity id
Discover workflows that lack an associated entity ID, which could indicate incomplete or misconfigured processes within your Jira workflow system. This can be useful to identify and rectify potential issues, ensuring smoother operations.
select name, entity_id, description, is_defaultfrom jira_workflowwhere entity_id = '';
select name, entity_id, description, is_defaultfrom jira_workflowwhere entity_id = '';
Schema for jira_workflow
Name | Type | Operators | Description |
---|---|---|---|
_ctx | jsonb | Steampipe context in JSON form. | |
description | text | The description of the workflow. | |
entity_id | text | The entity ID of the workflow. | |
is_default | boolean | Whether this is the default workflow. | |
login_id | text | =, !=, ~~, ~~*, !~~, !~~* | The unique identifier of the user login. |
name | text | = | The name of the workflow. |
sp_connection_name | text | =, !=, ~~, ~~*, !~~, !~~* | Steampipe connection name. |
sp_ctx | jsonb | Steampipe context in JSON form. | |
statuses | jsonb | The statuses of the workflow. | |
title | text | Title of the resource. | |
transitions | jsonb | The transitions of the workflow. |
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_workflow