Administrator Guide

All Power BI Connector for Jira settings can be made on one page, therefore the instructions below show how to find the plugin settings page and describe all available configurations.

 

 

Platform administrators always

  • have the ability to see any existing connectors in an instance

  • have the ability to modify any existing connectors in an instance

  • have the ability to delete any existing connectors in an instance

  • have the ability to edit share settings of any existing connectors in an instance

 

 

How to configure Power BI Connector for Jira?

 

You can get to the application settings page in 2 options:

 

1st Option

Click Power BI Tab on Jira’s main menu. Then choose Administration.

2nd Option

Step 1. Go to Jira Administration tab and select Manage apps section.

Step 2. On the left side menu panel find “Power BI Connector for Jira” tab and click Plugin settings.

 

Power BI Connector for Jira settings page

 

Below you will find a description of the Power BI Connector for Jira settings:

 

 

1. Reset to defaults

This action will restore plugin settings to defaults, delete all Data Sources and user permissions.

 

2. Edit user permissions

To be able to import data from Jira into Power BI Jira administrator should grant permission to create, edit, watch, and export connectors.

These settings grant users and groups permission.

  1. Select groups - start typing to find and add relevant users group.

  2. Select users - start typing to find and add relevant users.

  3. Save - apply permissions.

 

 

3. General Settings

Jira administrators have the ability:

  1. Set a maximum number of tickets(Issues Limit) that can be exported at an instance level.

  2. Set a Fields Threshold - a maximum number of fields that can be exported without a warning message.

  3. Save to apply settings

General Settings help to:

  • stop misuse of the addon

  • drop the considerable strain on JIRA

  • improve time to export

 

4. Logging Settings

A useful tool for debugging the plugin. It’s recommended to turn it on only for troubleshooting cases and to turn it off right after receiving enough data to analyze issues.

  1. Enable/disable data export debug mode - toggle to turn it on and off (debug mode affects the performance of the instance, so it’s highly recommended to turn it off after getting all necessary debug info).

  2. Enable/disable internal debug mode - toggle to turn on/off for logging all actions performed with data sources except data export (creating, editing, cloning, changing owner, etc.).

  3. Log File Size Limit - Maximum log file size (from 0 to 100 megabytes).

  4. Save to apply settings

  5. Refresh logs

  6. Clear logs

  7. Download logs so you can send them to the Power BI Connector for Jira support team

  8. Select file format (Log or Zip)

 

 

In order to minimize debug mode’s impact on the instance, please follow these simple steps:

  1. Create a data source with one selected table for analysis. It’s recommended to enable filtering to reduce data amount to export. See https://aserve.atlassian.net/wiki/spaces/POWERBI/pages/696713277 if you need detailed instructions on how to create a data source.

  2. Go to Logging Settings.

  3. Clear previous logs if any left, set a log file limit, save changes and enable debug mode.

  4. Open Power BI Desktop, start data export.

  5. After data export is completed, get back to Logging Settings, disable debug mode and download the file.

 

At the moment, the output of the following tables is being logged:

Jira Core

Jira Software

Service Management

Tempo

Insight

Xray

Tempo Budgets

Jira Core

Jira Software

Service Management

Tempo

Insight

Xray

Tempo Budgets

  • Issues (Issues, Issue Effort, Parent Issues, Epics)

  • Issue Links

  • Issue Custom Fields (Issues or custom table)

  • History (Histories, Time in Statuses, Time at Assignee)

  • Projects

  • Sprints

  • Sprint Issues

  • Boards

  • Board Charts

  • Sprint Report Charts

  • Burndown Charts

  • Board Issues

  • Approvers

  • Customer Request Type

  • Request Participants

  • Customer Request Type

  • Request Participants

  • Another Service Management Fields (Issues)

  • Tempo (Issues)

  • Teams

  • Object Schema

  • Object

  • Object Type

  • Object Type Attribute

  • Status Type

  • Role

  • Insight Attribute Value

  • Test Runs

  • Folios

  • Expenses

  • Human Resources

  • Rates

  • Allocations

 

5. Custom Fields Map

Select Custom Field defined as Story Points in your system.