Power BI Connector for Jira (Cloud)
Power BI Connector for Jira (Cloud)
Breadcrumbs

Upcoming Changes to Jira API Token

Overview

Atlassian has announced the deprecation of the Jira API token effective soon. This change is part of Atlassian’s broader transition from the legacy Connect framework to Forge, their cloud-native, serverless development platform. Because all cloud apps are required to move to Forge, this change is mandated by Atlassian and not initiated by our product.

As a result of the transition and the API token deprecation, some Jira data that was previously accessible may be impacted. These limitations affect many Jira-based apps and are not specific to our implementation.

🔗 Reference: See Atlassian Forge changelog (CHANGE-2728) for details

Important clarification about authentication

This change does not affect how the app authenticates in Microsoft Power BI.

  • The app will continue to use an access token for authentication in Power BI, and this mechanism remains unchanged.

  • The Jira API token is used by the app only to retrieve data from specific Jira endpoints that require it.

If you are not exporting tables that rely on those endpoints, no action is required and there is nothing to change in your authentication setup.

Impact on Functionality

Based on our investigation, some data may no longer be available once the Jira API token is deprecated. Atlassian does not currently provide replacements for certain endpoints, which means some functionality could be affected if no alternatives become available. However, we’re actively working with Atlassian to preserve existing functionality and minimize disruption wherever possible.

The following data may be impacted:

  • AQL filter validation

    • Assets data will still be available for export; however, the AQL filter validation functionality will be affected.

    • Due to the API token deprecation, we will no longer be able to return specific validation errors when an AQL query is incorrect. Instead, users will receive a generic error indicating that something is wrong with the filter.

    • Users can still test and validate their AQL filters directly in Assets.

    • If an export is performed using an incorrect AQL filter, the resulting export will return null values.

  • User profile-related tables

    • UserProfiles

    • UserProperties

  • Agile reporting data

    • VelocityCharts

    • BurndownCharts

At this time, there is no confirmed workaround for retrieving affected data if deprecation impacts specific endpoints.

How You Can Help

Some of these limitations could be resolved if Atlassian introduces new APIs. If this functionality is important to your workflows, we encourage you to vote on the corresponding Atlassian feature requests:

Engagement on these tickets helps Atlassian prioritize future improvements.

What to Expect

Atlassian may still revise or delay the deprecation timeline, but no changes have been confirmed at this time. To ensure transparency, we are informing users in advance so you can plan accordingly.

We continue to actively monitor the situation and collaborate with Atlassian. Our goal is to preserve existing functionality wherever possible, and we will update the documentation as soon as new guidance or replacement APIs become available.