Power BI Jira Connector app integrates with Insight (now Assets) in Jira Service Management. This integration further extends the capabilities of Insight asset and configuration management in the Jira cloud and DC/Server to visualize the required data for actionable insights in Microsoft Power BI. With this integration, Insight Attributes and Insight Types fields information can be imported to Microsoft Power BI.
...
Note |
---|
Pre-requisite to use Insight (Assets):
|
Steps to integrate Power BI Jira Connector and Insight in Jira Service Management
Info |
---|
|
...
2. To add a new connector to pull the required Insight fields, click Add New Connector. For more information about creating Connector URLs, refer to My Connectors.
...
3. A form is presented with Jira and JSM fields to create the Connector URL. The Insight Attributes and Insight Types list the insight fields.
Set up the connector for the Insight (Asset) fields
The steps below illustrate how to fetch the Insight (Asset) data to import into Microsoft Power BI.
Power BI Jira Connector Cloud
a. To import the Insight data, you must set up the Email and API Token once. Enter the Email and API Token to grant access to Insight dataand select the required Insight fields for the Connector URL. To save the Connector details, click Save and Close.
...
d. To save the connector details, click Save and Close. To know about the checks performed while saving the connector, refer to Form validation.
Power BI Jira Connector Data Center
a. To import the Insight data, select the required Insight fields for the Connector URL. To save the Connector details, click Save and Close.
...
d. To save the connector details, click Save and Close. To know about the checks performed while saving the connector, refer to Form validation.
Import into Power BI
To import the Insight data into Power BI, refer to Import into Power BI.
The Insight data imported through the Connector URL appears in Power BI as tables.
...
Anchor | ||||
---|---|---|---|---|
|
On the click of Save and Close, the form is validated for the Email and API Token and the AQL syntax in sequence before saving the connector.
...
The AQL syntax is validated once the Email and API Token pass the validation check. The error message is displayed if the AQL syntax is not valid. For more information about error handling, refer to AQL syntax validation.
...
Anchor | ||||
---|---|---|---|---|
|
Assets Query Language (AQL) is a language format used in Assets in Jira Service Management to create search queries for one or more objects.
Basic syntax
The basic syntax of an AQL query is <attribute> <operator> <value/function>. The query returns one or more objects when the attributes of these objects match the operator and value specified.
...
Example | Query | ||
---|---|---|---|
Limit the search result to a specific object schema name. |
| ||
Limit the search result on object schema ids. |
| ||
Limit the search result to a specific object type. |
| ||
Limit the search result on object type ids. |
| ||
Search all attributes on all objects for a relevant match. |
| ||
Limit the search to the object having any inbound references to it. |
| ||
Find an object by object Id. |
|
Anchor | ||||
---|---|---|---|---|
|
The Assets app manages the AQL syntax validation and error messages.
...
Example | Query provided with invalid syntax | Error message | ||
---|---|---|---|---|
Limit the search result to a specific object schema name. |
| |||
Limit the search result on object schema ids. |
| |||
Limit the search result to a specific object type. |
|