| Table of Contents | ||||
|---|---|---|---|---|
|
📘 As not all users have permissions to export Jira data, Jira Cloud Administrators can grant necessary permissions to work with Power BI Connector for Jira Cloud for specific users or groups. The instructions below demonstrate how to grant these permissions, allowing users to create, edit, watch, and export connectors.
Administrators have the permission to work with the connector by default.
| Panel |
|---|
| Info |
|---|
Read more on how to effectively connect Jira and Power BI Desktop ⬇️ |
General Settings
| ||||||||
Regular users can now view and search the history of their own and shared data sources. However, permission and access token expiry management remain in the Administration module. |
How to Grant Permissions
Being signed in to your Jira Cloud instance, select Apps, and then select Power BI Connector for Jira.
On the left-side menu, select Administration, and then select Edit.
In the Users field, enter the username you want to grant permissions to.
| Info |
|---|
You can select as many individual users as you need to. |
In the Groups field, select the groups you want to grant permissions to.
| Info |
|---|
You can select as many groups as you need to. |
Select Save.
| Info |
|---|
Here you can also view who has permission to work with Power BI Connector for Jira, edit , and revoke all permissions. |
How to Configure Access Token Expiry
📘 This feature allows admins to decide in how many days access tokens are to expire.
Being signed in to your Jira Cloud instance, select Apps, and then select Power BI Connector for Jira.
On the left-side menu, select Administration, and then select General settings.
| Info |
|---|
The access token expiry date is applied to all users. The default value is 365 days. |
If the administrator sets an expiry date of 10 days, this setting will affect all valid access tokens with expiry date later than 10 days from now, as well as tokens with no expiry date. All tokens with less than 10 days remaining won’t be affected.
If, later today, the administrator sets an expiry date of 20 days, no access tokens will be affected, because they were already set to 10 days.
If the administrator turns off the expiry setting, no existing tokens will be affected.
Data Sources History
Being signed in to your Jira Cloud instance, select Apps, and then select Power BI Connector for Jira.
On the left-side menu, select Administration, and then select Data source history.
| Info |
|---|
The tab displays all changes performed to the data sources by all users, including creating, editing the fields or filters, sharing, changing owner, and more. |
.gif?version=1&modificationDate=1720708289013&cacheVersion=1&api=v2&width=663)
Export History
Being signed in to your Jira Cloud instance, select Apps, and then select Power BI Connector for Jira.
On the left-side menu, select Administration, and then select Export history.
| Info |
|---|
The tab displays all data related to the export process: ID, user name, data source ID, tables count, rows count, and more. Filtering by statuses (All, Success, and Failed) and dates (Start date and End date) can help to find specific data. |
You can also apply search by data source name or table name.
Tokens History
Being signed in to your Jira Cloud instance, select Apps, and then select Power BI Connector for Jira.
On the left-side menu, select Administration, and then select Tokens history.
| Info |
|---|
Currently, this tab only reflects changes to the token expiration date. |
IP Whitelisting
Below are the current IP addresses used by the Power BI Connector for Jira Cloud application. We recommend whitelisting them only if you are experienced with the process and confident in managing it effectively.
| 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 GB: 3.9.52.5, 13.41.221.79 |
| Info |
|---|
Read more on how to effectively connect Jira and Power BI Desktop ⬇️ |