Power BI analytics templates for Jira teams who want a sharper view of delivery — without building the reporting layer from scratch.
Explore the Evaluation ↓These are the views the templates are built around: portfolio health, project drivers, and the issue flow underneath. The screenshots use an early dataset; the story gets much richer as Jira history accumulates.
Organize projects into meaningful portfolios—such as Delivery, Discovery, and Training—and see how each area is performing. Bring health, trends, risk, and delivery drivers into one clear view, so you quickly know where attention is needed.
Explore delivery by customer—such as Internal, GreenGrid Energy, Harborline Logistics, and others. Compare project health, assessment coverage, movement over time, and the exceptions driving each result. Your next customer or portfolio review starts with evidence.
Choose an As of month to see the project exactly as it stood at that point in time onwards—not only where it stands today.
Driver Exceptions & Explanations turns the score into plain-language signals: what is healthy, what needs attention, what is at risk, and the numbers behind each result.
Explore backlog age, workflow bottlenecks, priorities, issue types, and assignee workload. Then move straight to the open issues that need attention first.
Turn a Jira CSV export into portfolio, project and issue-level delivery insight in Power BI—without building the reporting layer from scratch.
The Evaluation loads Jira issues only. Worklogs are not included.
The Evaluation reads the local file path you provide to Power BI and does not write back to Jira. Never email passwords, credentials, confidential Jira data or an unredacted Jira export.
Local Jira CSV export
Direct Jira Cloud API
Manual CSV refresh
Refresh directly from Jira
Exploring the approach and validating fit
Repeated operational reporting
€69
€249
For setup, licence or purchasing questions, email demy.lab44@gmail.com.
Yes. Open the included sample PBIX first. Its synthetic data lets you review the finished report before preparing your own export.
No. The Evaluation reads the CSV you export and does not write back to Jira.
Yes. Project mappings and report views are designed to be adapted in Power BI.
No. Evaluation uses a local CSV export. API Connected refreshes directly from Jira Cloud and is a separate product.
Connect Power BI directly to Jira Cloud, define the dataset with JQL, and refresh the same portfolio, project and issue reporting experience whenever the conversation needs current data.
Power BI manages Jira credentials separately on each machine. Delivery Intelligence Lab never needs your token, password, Power BI credentials or confidential Jira data—and you should never send them by email.
For setup, licence or purchasing questions, email demy.lab44@gmail.com.
Choose Basic authentication in Power BI, enter the Atlassian account email as the username and use its API token as the password.
The initial JQL defines the dataset. The connected account must have permission to browse every project selected by that query.
No. Power BI stores credentials separately from the PBIT. API tokens and customer data are not included in the product package.
Power BI Service refresh requires separately configured credentials and a gateway where applicable.
Both editions use the same editable reporting model and real report views. The difference is how Jira issue data reaches Power BI and how often you need to refresh it.
Best when you want to explore the complete report, test your own authorised Jira export and adapt the model before committing to a connected workflow.
Explore Evaluation ↑Best when you need repeated Jira Cloud refresh through a controlled JQL scope, without preparing a new CSV export each time.
Explore API Connected ↑Evaluation and API Connected are the Jira Issues Analytics editions. Development now moves to Worklogs: adding time and effort context to the same delivery-intelligence approach.