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 January 1, 2026. 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 will no longer be available. These limitations affect many Jira-based apps and are not specific to our implementation.

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

Impact on Functionality

Based on our investigation, some data will no longer be available once the Jira API token is deprecated. Atlassian does not currently provide replacements for these endpoints, which means the affected functionality cannot be restored unless new APIs become available.

The following data will no longer be accessible:

  • 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

    • SprintReports

    • SprintReportIssues

    • SprintReportCompletedIssues

    • SprintReportRemovedIssues

    • SprintReportCompletedOutsideIssues

    • SprintReportIncompletedIssues

At this time, there is no known workaround for retrieving this data after deprecation.

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. To ensure transparency, we are informing users in advance so you can plan accordingly.

We will continue monitoring the situation and will update our documentation if Atlassian provides new guidance or replacement APIs.