Overview

Easy BI is an app that allows you to create and view business intelligence reports directly within Jira. This guide is designed for users who will be using custom reports to gain insights on their projects from their Jira data.

App usage

1. To begin using easyBI, go to Apps section on the header menu in Jira, and select easyBI.

2. Your main tab for interacting with the app is Dashboards. This section allows you to access the analytics for your projects.

In this tab you will find tabs for different users or groups. Initially, every PM on the team should have their project stats in the retrospective tab, and the Management tab contains stats on all the projects to see a bigger picture.

3. To create a new dashboard, press New in the top right corner of the page.

After that, you will be able to enter a title for the dashboard you are creating, add different kinds of reports, expand/collapse them for your comfortable usage, and save it.

4. Once you set up your dashboard, there are a few ways to interact with it:

• Drill down – click on data you’d like to see more detailed or go to source (open the issue, project or team member in Jira – the app will redirect you);

• Adjust filters – use the filters on top of the report to choose the needed settings (e.g. timeframe, project/epic, assignee, etc.);

• Download the report – you have 2 ways to do so:

  • Download the whole dashboard as you see it on the screen – press the download button in the top right corner of the screen (marked with pink on the screenshot) – in this case you can download PDF file.

  • Download only one widget you need – press the download button in the top right corner of the widget (marked with green on the screenshot) – in this case you can download CSV, XLS, or PDF file.

Widget creation

How to create the report that can be added to a dashboard later?

1. Go to Analyse tab on the top menu of easyBI. Open your folder, and press New report button.

2. Define the list of properties you want to reflect on the report, their timeframe and main filtering that you would prefer for your reports.

3. Define what properties you want to add as Columns, Rows, or Pages.

Pages – this section defines your ability to filter the report in the Dashboard. The properties in the Pages section will allow you to reflect only the data you need (especially if you want to be able to choose the timeframe, project, assignee, or any other property). – marked with pink on the screenshot.

Rows – this section defines what information you will see as rows of the table. In the report, the columns go in the same order as you configure the Rows section (e.g. on the screenshot we have the issue title first and the chosen measure is second). – marked with green on the screenshot.

Columns – this section defines what numbers you will see in the table . The number of columns will depend on the property that you choose and how detailed you will make it. E.g. in the screenshot we can see the amount of time spent on the tasks, in all statuses. But we also have the ability to drill the statuses section into every status possible, and the table will have more columns, when the amount of the rows will remain the same. – marked with orange on the screenshot.

4. Define the type of reflecting the widget. It can be table, progress bar, line diagram, pie chart, scatter, timeline, map, Gantt diagram, or gauge.

• Table – pretty simple, we all know what that means;

• Progress bar – comfortable to reflect progress, compare estimated/spent time, compare number of tasks/bugs, etc.

• Line chart – represents trends of a continuous data set.

• Pie chart – perfect to see the breakdown of the whole picture, see different parts of the whole project (e.g. how much we spent on FE/BE/QA).

• Scatter – can be used to reveal patterns, trends, and potential correlations.

• Timeline – shows us stats on the project reflecting the progress over time.

• Map – we do not have properties in issues with locations, so this one is useless for our team.

• Gantt – can be used to illustrate the progress over time.

• Gauge – can be used to reflect the KPIs for the team, when the gauge limit is set.

If you need a complex widget or cannot create the type of widget you need, please contact Viktoriia Khavaliuk with the request. The request should contain the set of information you would like to see in the report, the type of visualisation you prefer and the properties for filtering.

Widget sets

Here are a short description for every widget in our templates set, so that you can easily navigate within it.

Important! The widget sets described below are designed as templates. When you want to use a template – you can alter it to your preference, and in this case you should press SAVE AS, and save it into your folder with the naming you prefer. But the template should remain a template;)

Project

Widgets in this section are all filtered by projects – they reflect the data for the whole project unless there is a timeframe as filter.

1. # of Bugs VS CB VS CR – reflects number of bugs discovered by our QA team (issue type – Bug), number of bugs discovered by clients (issue type – CB), and number of client’s requests that were out of the initial project scope (issue type – CR).

• Filtered by Project;

• Type of the chart – Gauge.

2. # of issues in Statuses – reflects the number of issues in every status within the project.

• Filtered by Project;

• Type of the chart – Bar.

3. # of reopened tasks – reflects the number of issues that were reopened after completing due to the bugs fixing.

• Filtered by Project, Timeframe, Issue Type;

• Type of the chart – Gauge.

4. # of tasks opened after QA – reflects all the issues within a project that were opened by QA, so that you can see the list of bugs for a certain block or page.

• Filtered by Project, and Epic;

• Type of the chart – Table.

5. Estimated VS Spent – reflects the comparison between estimated and spent time on the project.

• Filtered by Project, and a Timeframe

• Type of the chart – Table.

6. Estimated VS Spent | Grouped by issue type – reflects estimated and spent time for a project, and how much was estimated/spent for every issue type and type of work (e.g., FE/BE/QA/TL/PM).

• Filtered by Project, and a Timeframe

• Type of the chart – Table.

7. Estimated VS Spent | Bugs + CR – reflects estimated and spent time for bugs and client requests within a project.

• Filtered by Project, and a Timeframe

• Type of the chart – Table.

8. Estimated VS Spent | CB – reflects estimated and spent time for bugs discovered by client within a project.

• Filtered by Project, and a Timeframe

• Type of the chart – Table.

9. Estimated VS Spent | CR – reflects estimated and spent time for client’s requests that were out of the initial project scope.

• Filtered by Project, and a Timeframe

• Type of the chart – Table.

10. Open VS Done – reflects the number of open/done issues and percentage of the project’s completion.

• Filtered by Project;

• Type of the chart – Bar.

---

Epic

The widgets in this section are all filtered by epic, so that they reflect data for an epic, and not the whole project.

1. # of issues filtered by issue type | Epic – reflects the number of issues of every issue type used in a project.

Type of the chart – Gauge.

2. # of Open VS Done – reflects the number of open/done issues and percentage of the epic’s completion.

Type of the chart – Bar.

3. Estimated VS Spent time | Epic – reflects estimated and spent time for an epic.

Type of the chart – Bar.

4. Time spent filtered by issue type | Epic – reflects time spent of completing issues of different types within an epic.

Type of the chart – Pie.

5. Time spent filtered by Quarters | Epic – reflects time spent for completing issues of different types over time. Filtered within an epic and reflected quarterly.

Type of the chart – Line.

6. User Spent time | Epic – reflects time spent on epic’s completion for every team member.

Type of the chart – Table.

7. User Spent VS Estimated time | Epic – reflects estimated and spent time for every issue in the epic, also includes issue’s reporter and the person who worked on it. Is filtered by project and timeframe.

Type of the chart – Table.

Sprint

1. # of tasks | Sprints – reflects the number of created and done/resolved issues.

Type of the chart – Gauge.

2. Estimated VS Spent – reflects the estimated and spent time for completing the tasks in a sprint. This widget is grouped by issue type and also has the time spent categorised for teams (BE/FE/QA/PM/TL).

Type of the chart – Table.

3. Time Spent by Users – reflects the time that every user spent working on the issues within a sprint as well as the statuses for every issue.

Type of the chart – Table.

Management

This folder contains the widgets created for the management team (co-founders and team leads).

Most of the widgets reflect the situation for the ongoing projects to see a bigger picture on the team’s performance.

PM folders

As for PMs' folders, every PM has a folder named after them, and containing the widgets that are made or customised specifically for them.

The folder with your name is the place where you should save widgets that you create or customise.