This article explains how the Epic related data are categorized after importing it into Power BI Desktop using Power BI Connector Pro for Jira app.
Log in to Jira and navigate to the global navigation Menu (on the top)→AIO Power BI → My Connector URLs. Please note that the access to the app is controlled by the Access Permissions option, which is accessible only to a Jira administrator. Users will not see the AIO Power BI menu item, if the group they belong to, is not selected. In this case, the Jira administrator can perform the below steps.
Click on Add New Connector.
Input the JQL and select the fields that are in the Epic section i.e., Epic Colour, Epic Link, Epic Status, Epic Name, Epic/Theme along with other fields.
Edit the connector name if required and click Save and Close to get the connector URL as shown below:
Copy the connector URL, open the Power BI and navigate to Get data → Other → OData Feed → Connect.
Paste the connector URL within the Basic and click OK.
Now, select the tables and click Load to import the data within the Power BI. In this case, according to the selected fields within the connector URL, the tables are displayed as below
The reason for the display of EpicTheme and Labels as separate tables is, the fields Labels and Epic/Theme can store multiple values in it. The other fields related to Epic such as Epic Colour, Epic Link, Epic Status, Epic Name stores a single value within them. So they are displayed under the Issues table.
The fields are categorized based on the values that are stored. That means, single or multiple values are displayed under the appropriate tables while importing into the Power BI.
If the field Epic/Theme has any values stored in it, the data is displayed under the EpicTheme as shown below:
For the other fields such as Epic Colour, Epic Link, Epic Status, Epic Name the data is displayed under the Issues Table as shown below (which ever issue has the relevant data, else it will show with no value):
To avoid delay in importing the data, adjust the JQL to fetch the results within a single project (project = KEY) or selecting the relevant fields only.