/
Display all Jira work items in Confluence in a table format

Display all Jira work items in Confluence in a table format

Confluence page displaying a table of Jira projects with columns for ID, project key, and project name.

What it's useful for 

Use Appfire's CLI family of apps to connect your systems. For example, you can link your Jira and Confluence data. This example shows you how to create a table of all your Jira projects on your Confluence space.

This is useful for:

  • Keeping your data in sync across all systems.

  • Getting a centralized overview of all projects to streamline prioritization and resource allocation.

  • Improving cross-team collaboration and increasing transparency.

  • Presenting a complete list of all projects for compliance, auditing, and future analysis.

What’s unique

  • Connect your Jira and Confluence instances by running commands from the centralized ACLI Shell.

  • No need to click around in your Jira and Confluence user interfaces.

  • Run simple, text-based commands from the terminal interface and get the job done quickly.

To get started

  1. Install Jira CLI and Confluence CLI.

  2. Download the ACLI to run commands.

  3. Use getIssueList to get the work item list from Jira.

Example command:

-a run -i "myjira -a getIssueList --jql project=project_key --columns 1,2,3,4 --outputType html -f @temp" -i "myconf -a storePage --replace --space space_key --title title_name --parent @home --noConvert -f @temp"

Parameters used in the CLI action: 

  • jql - input the JQL query that you want to display the list on the Confluence page.

  • columns - specify the column names you want to display.

  • outputType - specifies the output format type. Valid values are: text, table, HTML, JSON, and variables.

  • space - enters the space key.

Use storePage to create or update a Confluence page.

Example command:

-" run -i "myjira -a getIssueList --jql project=TESTMKJMWE --columns 1,2,3,4 --outputType html -f @temp" -i "myconf -a storePage --replace --space SPAC --title SPAC  --parent @home --noConvert -f @temp"

 

We recommend testing this scenario in a non-production environment, or run the action with the --simulate parameter, to verify the behavior before deploying in a production environment.