Knowledge Base Articles
Knowledge Base Articles
Breadcrumbs

Deprecation of Jira API token and its difference from access token - BigQuery Connector

Question

We are currently using your connector to pull Jira data into BigQuery using API token-based authentication.

We have received a warning indicating that API token usage will be deprecated effective January 1st, 2026. However, at present, our existing API token is still working correctly, and we are able to access Jira data without any issues.

Could you please help clarify the following:

  1. Is the API token deprecation fully enforced as of January 1st, 2026, or is this part of a phased rollout/grace period?

  2. Until when will existing API token-based connections continue to work?

  3. What is the recommended authentication method going forward?

  4. Is there a migration guide or timeline available for updating existing connections?

  5. Will any action be required from our side to avoid service disruption?

We would like to proactively plan the migration to ensure uninterrupted data refreshes.

Answer

The Jira API token and access token are different. The access token acts as a password, while the API token helps to fetch specific tables within the application. There are no changes planned to the authentication process or access token.

It is the Jira API token, which will be deprecated. Once it is done, the following will no longer be available to the connector:

  • User profile tables: “UserProfiles”, “UserProperties”.

  • Agile reporting tables: “VelocityCharts”, “BurndownCharts”, “SprintReports”, and all “SprintReport*” tables (”SprintReportIssues”, etc.)

  • AQL filter validation details: Specific error messages for AQL filter validation will be unavailable (Assets export will still work, but invalid filters will return nulls).

However, the good news is that it did not occur on 1 January 2026. We are actively working with Atlassian on this matter and have reached a temporary agreement to avoid an immediate interruption of exports on that day. This is not yet a final resolution, and discussions are ongoing.

For reports relying on the affected user profile or agile reporting tables, we recommend planning replacements as soon as possible.

Action: Document visuals/measures reliant on these specific tables and redesign those reports to use alternative Jira issue fields or data from other apps.

Workaround: Currently, there is no known workaround to retain access to these particular tables after deprecation.

If this functionality is critical to your workflows, you can give your vote for the corresponding Atlassian feature requests to help them prioritize future API development:

  • AQL access improvements: JSDCLOUD-17971

  • Organizational data API: JSDCLOUD-17972

  • Custom user properties API: JRACLOUD-96616

  • Agile reporting data: JRACLOUD-96617