Pivot Report for JIRA.
Status overview and detailed breakdowns for all types of issues

Quick facts about Pivot Report

Over 7000 users from 40+ countries
Works both for small teams and large companies
Cloud and Server versions available
Zero bug policy. You report it, we fix it ASAP. Typically fixes take 1-3 days
Customer driven development. We are extremely proud to say that about 50% of features in the Pivot Report originated from customer requests

Typical management questions are:

1. What is current status of the tasks you or your team is working on?
What is done, what is yet left to do and how long it will take

2. Who did what?
Any task may have multiply assignees, and sometimes it's hard to figure out who was actually involved

3. Is there anyone with too many or too few things to deal with?
Who is doing what, and who has the most of it

4. Is there any time planning flaws like underestimated, unassigned or overdue issues?
Overdue, underestimated or unassgined issues may lead to unexpected delays in the development.

Typical solution is:

Perform number of searches for corresponding issues with JQL. Then check several reports for status overview: Velocity, Burndown, Workload, Worlogs, etc.

Addionaly you may need to export the data and build couple of pivot tables in Excel. And add some charts on top. And print it out somehow.

And yes, it typically works, but takes way too much time and kills any enthusiasm.

The better way

How do we know these questions? Well, we’ve been in your shoes for over a decade. And at some point we realized we don’t want to spend any extra second on answering these questions.

So we decided to create a tool that will help us get answers, fast. And this is how Pivot Report appeared.

Big picture for your issues

A set of different perspectives that shows you all aspects of the scope.

Awesome pivot tables in а couple of clicks

Pivot tables are great for issue analysis, but building them requires time. With Pivot Report you get handy tables in no time!

Multiple progress indicators

You need to see Velocity and Completion Rate? And also remaining time? No problem – combine and organize multiplе progress indicators as needed

Highlights for potential risks and flaws

Tired of looking for overdue, underestimated or unassgined issues with filters? With Pivot Report you’ll see such issues with no effort at all

Reports are always close to the issues you work with

Reports can be built in a couple of clicks right from:

Pivot Report is split into several tabs that show different aspects of the issue scope:
  • Issues Structure
  • Pivot
  • Worklogs
  • Warnings

Issues Structure

Display the scope in the hierarchy view for better understanding of parent and child issues relations.
Works for any issue setup you may have. Scrum Epics, Portfolio for JIRA and ALM Works Structure are supported out of the box.


Pivot tables are great for issue analysis and calculations, but building them requires time. With Pivot Report you get handy tables in no time.
This tab contains a Summary pivot table with customizable rows, columns and values.
Each row also has a corresponding Breakdown table with customizable columns. All cells have automatically calculated totals.


Spent time in JIRA may be confusing. First of all, an issue may have time logged from multiple assignees. Also, total spent time is not equal to time spent in a given period. In both cases a single value for Spent time is not enough to understand what is actually going on.

The Worklog tab allows you to see time spent by each individual in a specified period. Like the Pivot tab, it has two sections: Summary and Breakdown with detailed information about issues of each specific assignee involved


Let’s face it: no plan is ever perfect. Real life development always involves a fair portion of chaos like overdue or underestimated issues. Some issues are never assigned, some get forgotten.

You have to carefully check the scope to find and fix such issues. While Pivot Report can’t help you with fixing the source of the problems, it can help you a lot to find such flaws with no effort.

How to start using Pivot Report

Pivot Report is always close to the issues you're working on in JIRA. You can create the report right from:

Check the sections below for details, or can try it yourself in the demo project. No login required, feel free to browse for other issues and build the reports for them.

Build the report directly from the issue

Click on Pivot Report button in the top right corner in any open issue to open the report:

Build from filter/search

Click on Pivot Report button in the top right corner:

Pivot Report will search for all related tasks in both directions: "up" for parent and epic links and "down" for sub-tasks. So you need to pick the options for related issues and estimates:

You can try building the report from JQL in the Issue Navigator in the demo project. No login required.

Build the report from the Agile Board

You can also build Pivot Report directly from the board. Click on the Pivot Report button in the top right corner as shown below. Since boards have multiply sprints, you need to specify which one you need:

Pivot Report for ALM Structure

The Structure add-on from ALM Works supports export to external plugins. Thanks to that feature Pivot Report is seamlessly integrated to Structure. :

With Pivot Report you'll get same issue structure with Progress metrics and all other features:

Pivot Report for JIRA Cloud is Atlassian Connect Add-On (Add-On) Software as a Service (SaaS).

Data Security

The Add-On is static, so all data is requested from JIRA Cloud and processed by add-on client side in End User Browser and is not passed anywhere else.

  • Add-On declares READ scope to access issues' data.
  • Add-On also declares WRITE scopes to manage user's settings for the report itself.
  • Add-on persists add-on configuration (group names, link or field names selected in add-on configuration) in JIRA Cloud itself using Hosted Data Storage service.
  • There is no usage data collected by the add-on at all.


Atlassian OnDemand Security

1.Agreement Overview

This Agreement represents a Service Level Agreement (SLA or Agreement) between Dmitry Astapkovich and Customer for the provisioning of IT services required to support and sustain Pivot Report for JIRA.

This Agreement remains valid until superseded by a revised agreement mutually endorsed by the stakeholders.

This Agreement outlines the parameters of all IT services covered as they are mutually understood by the primary stakeholders. This Agreement does not supersede current processes and procedures unless explicitly stated herein.

2.Goals Objectives

The purpose of this Agreement is to ensure that the proper elements and commitments are in place to provide consistent IT service support and delivery to the Customer(s) by the Service Provider(s).

The goal of this Agreement is to obtain mutual agreement for IT service provision between the Service Provider(s) and Customer(s).

The objectives of this Agreement are to:


The following Service Provider(s) and Customer(s) will be used as the basis of the Agreement and represent the primary stakeholders associated with this SLA:

4.Periodic Review

This Agreement is valid from the Effective Date outlined herein and is valid until further notice. This Agreement should be reviewed at a minimum once per fiscal year; however, in lieu of a review during any period specified, the current Agreement will remain in effect.

The Business Relationship Manager (Document Owner) is responsible for facilitating regular reviews of this document. Contents of this document may be amended as required, provided mutual agreement is obtained from the primary stakeholders and communicated to all affected parties. The Document Owner will incorporate all subsequent revisions and obtain mutual agreements / approvals as required.

Business Relationship Manager: Dmitry Astapkovich

Review Period: Yearly (12 months)

Previous Review Date: 22 Jan. 2017

Next Review Date: 22 Jan. 2018

5.Service Agreement

The following detailed service parameters are the responsibility of the Service Provider in the ongoing support of this Agreement.

5.1.Service Scope

The following Services are covered by this Agreement;

Monitored email support

5.2.Service Assumptions

Assumptions related to in-scope services and/or components include will be communicated and documented to all stakeholders.

6.Service Management

Effective support of in-scope services is a result of maintaining consistent service levels. The following sections provide relevant details on service availability, monitoring of in-scope services and related components.

6.1.Service Availability

Coverage parameters specific to the service(s) covered in this Agreement are as follows:

6.2.Service Requests

In support of services outlined in this Agreement, the Service Provider will respond to service related incidents and/or requests submitted by the Customer within the following time frames:

We are always ready to hear you. Please feel free to send us your feedback via email to support@colined.com.

Email is monitored 10:00 A.M. to 7:00 P.M. (MSK, UTC +3) Monday – Friday.

Also we track all comments you post on our product page on Atlassian Market . Never hesitate to give us feedack there!

And you can leave your comments here as well, we'll reply you as soon as possible!