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.
Power BI Jira Connector Cloud and DC/Server app (version 4.1.0 and above) offers Insight integration.
Power BI Jira Connector requires Microsoft Power BI Desktop software to function.
Pre-requisite to use Insight (Assets):
To use Assets for the Jira Cloud, you need to have Jira Service Management Cloud Premium or Enterprise. For more information, refer to Assets in Jira Service Management.
To use Assets for the Jira Data Center, you need to install Jira Service Management Data Center 4.15 or above. For more information, refer to Assets for Jira Service Management Data Center.
Steps to integrate Power BI Jira Connector and Insight in Jira Service Management
Insight is now called Assets. For more information, refer to Insight is now called Assets.
It is required to define a custom field in Jira to import the values of Insight Attributes and Insight Types.
Administrators can define the number of Insight (Asset) Objects to be pulled for the Insight Attributes. For more information, refer to App Settings.
Navigate to Jira > Power BI Jira Connector > Connectors > My Connectors.
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 Connector URLs.
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 data and select the required Insight fields for the Connector URL. To save the Connector details, click Save and Close.
To generate a token, click Email and API Token.
Make sure to use the current instance's valid Email and API token. Providing invalid details will result in not fetching the Insight data. To know about the checks performed before importing Insight data, refer to Form validation.
You can Change API Token for Connectors if required.
b. Insight Attributes
Insight Attributes define an Insight object type. Each object type has its own set of attributes. For more information, refer to Understand how Assets is structured.
AQL for Insight (Asset) Objects: Provide the AQL query to filter the Insight Objects data. To validate the AQL, click Validate AQL Syntax. On successful validation, an ✅ appears.
AQL for Insight (Asset) Objects is available from version 4.2.0.
If the AQL query syntax is not correct, an error message appears. For more information, refer to AQL syntax validation.
Click
to know more about Asset Query Language syntax and usage. Refer to How to use Asset Query Language syntax.
Select the required Insight Attributes to import.
c. Insight Types
Insight Types defines the objects that the object schema contains. For more information, refer to Understand how Assets is structured.
Insight (Asset) Object Schemas: The Insight (Asset) Object Schemas drop-down lists all the available Object schemas in the Assets. The default value is All schemas.
You can select one or multiple Insight Object Schemas.
The Insight Object Schemas drop-down value is set to the default value of All schemas if:
None of the Object schemas is selected.
The selection consists of All schemas and any other Object Schemas.
Select the required Insight Type fields to import.
The Object Schemas drop-down lists only the default value of All schemas when creating a new connector. To view all the available schemas in the drop-down, Save and Close the new connector and open it again in the Edit mode.
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.
b. Insight Attributes
Insight Attributes define an Insight object type. Each object type has its own set of attributes. For more information, refer to Understand how Assets is structured.
AQL for Insight (Asset) Objects: Provide the AQL query to filter the Insight Objects data. To validate the AQL, click Validate AQL Syntax. On successful validation, an ✅ appears.
AQL for Insight (Asset) Objects is available from version 4.2.0.
If the AQL query syntax is not correct, an error message appears. For more information, refer to AQL syntax validation.
Click
to know more about Asset Query Language syntax and usage. Refer to How to use Asset Query Language syntax.
Select the required Insight attributes to import.
c. Insight Types
Insight type defines the objects that the object schema contains. For more information, refer to Understand how Assets is structured.
Insight (Asset) Object Schemas: The Insight Object Schemas drop-down lists all the available Object schemas in the Assets. The default value is All schemas. Select the Object Schemas.
Select the required Insight Type fields to import.
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.
Form validation
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 error message is displayed if the Email or API Token values are invalid. To proceed to the next step, provide valid credentials.
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.
How to use Asset Query Language syntax?
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.
To know more about Assets Query Language, refer to
Using Assets Query Language (Cloud)
Advanced searching: AQL - Assets Query Language (Data Center and Server)
Example | Query |
|---|---|
Limit the search result to a specific object schema name. | objectSchema = "ITSM Schema" |
Limit the search result on object schema ids. | objectSchemaId in (1, 2) |
Limit the search result to a specific object type. | objectType = "Employment Start Date" |
Limit the search result on object type ids. | objectTypeId in (1, 2) |
Search all attributes on all objects for a relevant match. | "anyAttribute = 123.123.123.123" |
Limit the search to the object having any inbound references to it. | "object having inboundReferences()" |
Find an object by object Id. | "objectId = 114" |
AQL syntax validation
The Assets app manages the AQL syntax validation and error messages.
Once you provide an AQL query, to validate the syntax, click Validate AQL Syntax.
If you skip manually validating the AQL syntax, the form validation is performed with the click of Save and Close.
If the AQL syntax is correct, then ✅ is displayed.
If the AQL syntax is not correct, an error message is displayed. To proceed to the next step, provide valid AQL query syntax.
A few error messages are listed below based on the type of syntax errors.
Example | Query provided with invalid syntax | Error message |
|---|---|---|
Limit the search result to a specific object schema name. | objectSchema = |  |
Limit the search result on object schema ids. | objectSchemaId in |  |
Limit the search result to a specific object type. | objectType = "IT |  |