Table: jira_project_role - Query Jira Project Roles using SQL

Jira Project Roles are a flexible way to associate users and groups with projects. They allow project administrators to manage project role membership. Project roles can be used in permission schemes, issue security levels, notification schemes, and comment visibility.

Table Usage Guide

The jira_project_role table provides insights into project roles within Jira. As a project administrator, explore role-specific details through this table, including permissions and associated users and groups. Utilize it to manage project role membership, and to set up permission schemes, issue security levels, and notification schemes.

Important Notes

Project roles are somewhat similar to groups, the main difference being that group membership is global whereas project role membership is project-specific. Additionally, group membership can only be altered by Jira administrators, whereas project role membership can be altered by project administrators.

Examples

Basic info

Explore the different roles within your Jira project. This can help in understanding the distribution of responsibilities and in managing team members more effectively.

select
  id,
  name,
  description
from
  jira_project_role;

select
  id,
  name,
  description
from
  jira_project_role;

Get actor details

Explore the details of different actors within your Jira project roles. This query is useful for gaining insights into the identities and account IDs of actors, aiding in project management and team coordination.

select
  id,
  name,
  jsonb_pretty(actor_account_ids) as actor_account_ids,
  jsonb_pretty(actor_names) as actor_names
from
  jira_project_role;

select
  id,
  name,
  actor_account_ids,
  actor_names
from
  jira_project_role;

Get actor details joined with user table

This query is used to identify the details of actors from the user table in a Jira project. It can be useful in understanding the roles and statuses of different actors in the project, which can aid project management and team coordination.

select
  id,
  name,
  actor_id,
  actor.display_name,
  actor.account_type,
  actor.active as actor_status
from
  jira_project_role as role,
  jsonb_array_elements_text(actor_account_ids) as actor_id,
  jira_user as actor
where
  actor_id = actor.account_id;

select
  role.id,
  role.name,
  actor_id.value as actor_id,
  actor.display_name,
  actor.account_type,
  actor.active as actor_status
from
  jira_project_role as role,
  json_each(role.actor_account_ids) as actor_id,
  jira_user as actor
where
  actor_id.value = actor.account_id;

Schema for jira_project_role

Name	Type	Operators	Description
_ctx	jsonb		Steampipe context in JSON form.
actor_account_ids	jsonb		The list of user ids who act in this role.
actor_names	jsonb		The list of user ids who act in this role.
description	text		The description of the project role.
id	bigint	=	The ID of the project role.
login_id	text	=, !=, ~~, ~~, !~~, !~~	The unique identifier of the user login.
name	text		The name of the project role.
self	text		The URL the project role details.
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_project_role