Forum Discussion
powerbi data source error using JIRA powerBI connector
- Anonymous1 year ago
Hi AgileWorld,
Thank you for reaching out to the Microsoft Fabric Forum Community. Thanks to Poojara_D12 and GilbertQ for Prompt and helpful responses.
You don’t need to install any ODBC drivers if you’re using the JIRA connector with OData in Power BI. OData and ODBC are completely different, and your setup doesn’t rely on ODBC at all.If your JIRA is cloud-based, you usually don’t need to use a gateway. Just go to the Power BI Service, find your dataset, and update the data source credentials. Most of the time, it works with Basic or Anonymous authentication. Also, make sure the privacy level for the data source is set to Public to avoid permission issues.
However, if your JIRA is hosted on-premises (inside your company’s network), then you do need a data gateway. This gateway must be installed on a machine that can access your JIRA server. Make sure the gateway is up and running, and then go to the Gateway settings in Power BI Service and add the JIRA OData URL as a data source. Below documentations may help in resolving the issue.
https://learn.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem-tshoothttps://learn.microsoft.com/en-us/power-query/connectors/odata-feed
https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-install
Best regards,
Prasanna Kumar - Anonymous1 year ago
Hi AgileWorld,
Just following up to see if the responses provided by community members were helpful in addressing the issue.
If one of the responses helped resolve your query, please consider marking it as the Accepted Solution. Feel free to reach out if you need any further clarification or assistance.
Best regards,
Prasanna Kumar
Hi AgileWorld
The error you're encountering — "DM_GWPipeline_Gateway_RuntimeCheckFailedError" — during a refresh using the JIRA Power BI connector typically indicates that the Power BI service is unable to access the data source because of a missing or misconfigured gateway, or the data source settings do not align with how the connector is configured in Power BI. This issue often occurs when you're using a custom connector (like for JIRA) and have published the report to the Power BI Service, but the required on-premises data gateway is either not installed, not configured properly, or not recognized as compatible with the data source.
To resolve this:
-
Ensure the gateway is installed and running on a machine with access to JIRA.
-
In the Power BI Service, go to the dataset settings, check under “Gateway Connection,” and confirm that the correct gateway cluster is selected and online.
-
Verify that the data source is added to the gateway with the exact same connection parameters (URL, authentication method, etc.) as in Power BI Desktop.
-
If you're using a custom connector (.mez file) for JIRA, ensure it is deployed properly in the gateway’s custom connectors folder and that “Allow user extensions” is enabled in the gateway config.
Also, ensure your connector version matches the environment setup (e.g., OAuth authentication compatibility), and check for logs in the gateway log files if deeper debugging is needed. If none of this works, it's helpful to test the connector locally and also review any service limitations with JIRA APIs or throttling that may be causing the runtime to fail during scheduled refresh.