Power BI dashboard templates, supported with pre-configured data sources, are now available in this latest version. We are happy to introduce the new and exciting Power BI Jira reporting experience!

Build your first Power BI dashboard in a day with Jira Power BI dashboard templates in Power BI Connector for Jira from Alpha Serve!

How to Use Power BI Templates

• Being signed in to your Jira instance, select Power BI, and then select Templates.

• Select the template you would like to use, and then select Create Data Source.

Step 1. Generate data source

• In the Name* field, enter the name of your data source.

• In the Description field, enter the description for your data source if needed.

• In the Projects field, select the project you need.

• Select Next.

Step 2. Download Dashboard Template File

• Copy the generated URL of your data source, and then select Next.

• Launch your Microsoft Power BI Desktop, and then select File.

• Select Import, and then select Power BI template.

• Paste the data source URL copied before to the corresponding field, and then select Load.

• Select the Basic type of authentication, and then follow the steps described here starting from step 4.

Jira Dashboard Templates Description

Jira Project Dashboard

Jira Project Dashboard is a project overview report that allows one to get an instant overview of all or certain projects in the Jira instance. It shows the main KPIs for the selected projects. 

This dashboard will be useful for project managers and team leaders. It allows users to monitor the issues based on their type or priority, track the project progress and control the work resources allocation.

Jira Project Dashboard template can also be used to build Jira dashboard for multiple projects that are challenging in the default Jira reporting. With Power BI Connector for Jira, it is possible to build any multiple projects dashboard that you need in Power BI.

Jira Service Management Dashboard

Jira Service Management Dashboard shows the major service level indicators for the definite Jira ITSM projects. It will be useful as a daily monitoring tool for team leaders of the support or customer accounting teams, as it visualizes the total number of open and closed tickets, their share division, and their division by types or priority. 

The SLA indicators are also included in this dashboard, such as Average Time to Resolution (Estimated and Actual), including by Assignee, or types of issues created by type.

Jira Sprint Dashboard

Jira Sprint Dashboard shows the main metrics used to monitor the sprint progress (for the current sprint) or sprint results (for the completed sprints). 

It is useful for team leads and project managers to monitor sprint progress or analyze the finished sprint in retrospect.

Jira Sprint Time Report

Jira Sprint Time Report is a time tracking report Jira sprint. It shows timing progress on the sprint and the comparison of the original estimates and actual performance in a certain sprint. It allows users to see the time efforts on each issue and the time load per assignee. 

Jira Work Log Report/Jira Time Work Report

Jira Time Work Report shows the timing and workload per a particular assignee. It is a Jira work log report that can be applied to a certain project and/or the selected period of time. It is flexible in selecting the weekend days, as they differ in some countries. This may be used as a configurable alternative for timesheets in Power BI.

Jira Cumulative Flow Diagram

The Cumulative flow diagram shows the various statuses of the Jira project's issues over time. It's a visual indication of how many issues are passing through each status, thus, through the column of your project board. This helps users see which columns accumulate more issues than others, and identify bottlenecks in your team's workflow - and take actions accordingly and on time.

Jira ITSM Issues Created Report

Issues Created Report is one of the most widely used reports in Jira. It shows the full issues overview per certain project and period of time, the share of issues per type and/or priority. It is used by support teams to monitor workload as well as development quality based on users' requests.