Jira GDS Connector

Work backwards

A Press Release announcing the finished product

Jira to Google Data Studio Connector

Unlock the power of your data stored in Jira with interactive dashboards and beautiful reports on GDS that inspire smarter decisions.

Jira’s build-in reporting is great but still limited. Many teams export Jira data to Excel or Google Spreadsheet for further analysis. That is convenient but you have to export the data repeatly. This plugin enables realtime data sync to Google Data Studio and provides pre-defined report template that you could give you inspiration.

Note that on our road map in the next release you will be able to define dimensions that you want to keep a history that otherwise would have gone forever.

Problem

Jira collects a wealth of information that can help provide insights into your teams/organizations and substantially accelerate your process improvement and performance. Unfortunately, much of this information is hidden or difficult to retrieve in a usable form. The Jira Search tool/JQL provides you with some ability to get at the data, but it is still quite limited and cumbersome to use. Exporting queries is clunky and in most cases, you are restricted to exporting no more than 1000 rows (?ref).

In addition to all the aforementioned limitations, neither the reporting nor the query language let you get at the history detail which in our opinion is the most valuable data in the system.

Solution

Jira to Google Data Studio Connector (JDSC) allows any Jira user (that has installed JDSC plugin) to easily pull the information they need out of Jira, with no programming required, into Google Data Studio where they can manipulate it any way they like.

JDSC utilizes existing JQL queries to retrieve the data without the 1000 row export limit. It allows you to configure what Jira fields are to be included, how to format the retrieved fields, what names to use for the column headers, and how the underlying workflows will be mapped to cycle and lead time.

In addition to the fields that are normally available through the native Jira Search tool, JDSC provides access to data elements that are available only via the Jira APIs. That tool can access any custom fields you may have created in your Jira instance. Finally, JDSC provides a set of special derived fields that are not available directly.

JDSC also comes with predefined report templates that are good starting points for most use cases.

Unlock the power of the data and provide insights with built-in reports, that is what we provide.

How to get started

  1. Find JDSC on the marketplace and install it to your Jira instance (requires admin permission);

  2. On the top menu, you will see the “Reports in Google DS” item (only if you have permission);

  3. Click this menu, it will ask you to log in to Google DS;

  4. Once you logged, you will see the reports that are available.

  5. You can also create your own reports using Jira as data source.

Customer’s quotes

This is a missing feature on Jira! The moment that I see the new report I fall in love with it. It makes my life so much easier to prepare the report for the leadership team and for sprint planning. – Rose, BA

We always know there are more data hidden in Jira. We just didn’t know how to make it usable. This is a brilliant tool that mines the valuable data and reports them in an insightful way. – Ben, PM

Closing

Thanks for attending the release press conference. Now you can install the plugin on your Jira instances and enjoy the beautiful reports!

  • Heading - Name the product in a way the reader (i.e. your target customers) will understand.

  • Sub-Heading - Describe who the market for the product is and what benefit they get. One sentence only underneath the title.

  • Summary - Give a summary of the product and the benefit. Assume the reader will not read anything else so make this paragraph good.

  • Problem - Describe the problem your product solves.

  • Solution - Describe how your product elegantly solves the problem.

  • Quote from You - A quote from a spokesperson in your company.

  • How to Get Started - Describe how easy it is to get started.

  • Customer Quote - Provide a quote from a hypothetical customer that describes how they experienced the benefit.

  • Closing and Call to Action - Wrap it up and give pointers where the reader should go next.

Design elaborations

Risk

Description

Comments

 

Description

Comments

 

Not all users have Google DS experience; even if they have, the organisation might not allow Jira data to be exported.

We already see people asking on https://medium.com/@michael_41997/hi-michael-eee4286c70fb

 

 

 

 

Reference documents

Doc Link

Doc name

Comment

Doc Link

Doc name

Comment

https://www.product-frameworks.com/Amazon-Product-Management.html

Work backwards from Amazon

 

https://developer.atlassian.com/cloud/jira/platform/oauth-2-authorization-code-grants-3lo-for-apps/

OAuth2 for Jira

 

https://developers.google.com/datastudio/connector

Developer’s tutorial for GDS connector

 

https://community.atlassian.com/t5/Jira-questions/Is-there-a-way-to-connect-a-Jira-report-to-Google-Data-Studio/qaq-p/1019128

A real users asks for it.

 

https://www.stitchdata.com/integrations/jira/google-data-studio/

https://skyvia.com/data-integration/analyze-jira-with-google-data-studio

Generic connectors (potential competitor)

Not really concerned by generic connector. We should focus on a. connector, b. experience-based boards. The latter is a huge advantage.

 

 

 

https://michael-boumansour.medium.com/tapping-into-jiras-hidden-treasure-567f5fbf9066

Much of the problem and solution definition is from here.

@kushagra mehra (Unlicensed) Highly recommended for a reading.