Since not all users have permissions to export Jira data, Jira Cloud administrators can grant these permissions to work with the Looker Studio Connector for Jira Cloud to specific users or groups.
The instructions below explain how to grant the necessary permissions to work with the connector, including ability to create, edit, watch, and export connectors.
Info |
---|
Administrators have default permissions to work with the connector. |
Table of Contents | ||||
---|---|---|---|---|
|
How to Enable Looker Studio Connector for Jira and Grant Permission to Jira Users
Being signed in to your Jira Cloud instance, select the Apps drop-down menu, and then select Looker Studio Connector for Jira.
On the left-side menu, select Administration.
On the right side of the page, select the Edit icon.
The Edit permissions pop-up window will appear.
In the Users field, enter the username you want to grant permissions to.
Info |
---|
Once you start typing, the drop-down list with usernames suggestions will appear. Select the user from the list. You can select as many individual users as you need to. |
In the Groups field, select group you need.
Info |
---|
Once you select the Group field, the drop-down list with available groups will appear. Select group from the list. You can select as many groups as you need to. |
Select the Save button.
How to Check Who Has Permissions to Work with Looker Studio Connector for Jira
You can always check who has permissions to work with the Looker Studio Connector for Jira.
Being signed in to your Jira Cloud instance, select the Apps drop-down menu, and then select Looker Studio Connector for Jira.
On the left-side menu, select Administration.
Info |
---|
The required information will be depicted displayed in the middle part of the page under the Permissions section. |
How to View the Data Sources History
Being signed in to your Jira Cloud instance, select the Apps drop-down menu, and then select Looker Studio Connector for Jira.
On the left-side menu, select Administration.
Select the Data Sources History tab.
How to View the Export History
Being signed in to your Jira Cloud instance, select the Apps drop-down menu, and then select Looker Studio Connector for Jira.
On the left-side menu, select Administration.
Select the Export History tab.
Info |
---|
All data related to the export process will be displayed, namely ID, User name, Data source, Tables count, Rows count, Duration, Start date, and End date. |
You can also filter export processes by using the Start date and the End date fields. It might be helpful in finding specific data.
Export history can be filtered by the All, Success, or Failed processes. You just have to select one you need.
Configure Tokens to Export Add-Ons Data
Looker Studio Connector for Jira supports data export from the leading marketplace add-ons.
Info |
---|
View the complete list on the Supported Add-Ons page. |
Jira users must configure each add-ons separately to include Jira app data to their export to Looker Studio.
Tempo apps configuration
Projectrak app set-up
Time in Status app configuration
Zephyr Scale token
Xray app set-up
IP Whitelisting
IP allowlisting provides an additional level of control, enabling you to specify the IP addresses that users have to use to access content in Jira Software, Jira Service Management, and Confluence. When you establish an allowlist for Jira Software Premium, it also applies to customer and agent-facing portals for your Jira Service Management on the same site.
Here are the current IP addresses for Looker Studio Connector for Jira application instances. Please include these IPs to your IP allowlisting.
Code Block |
---|
Default region (Oregon): 35.161.7.18, 35.85.205.110 EU: 52.211.33.183, 54.77.134.91 DE: 18.184.153.1, 54.93.142.16 AU: 52.63.173.131, 54.253.130.102 SG: 18.138.139.163, 18.139.93.202 |
To view your IP allowlists:
Go to admin.atlassian.com
Select your organization.
If you have more than one organization you need to select one where I’d like to view your IP allowlists.
Select Security, and then select IP allowlisting.
Info |
---|
You will be able to access admin.atlassian.com even if the IP is outside the range of the allowlist. |