Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to migrate to the new Atlassian Data Lake schema

In a previous post, we announced that we'll release an improved version of the Atlassian Data Lake schema. The new schema will make it easier to query and build charts by reducing the need for complex joins and calculations. With the rollout of the new schema, all charts querying your existing Data Lake connections will break.

The best way to move forward is to create a new Data Lake connection to get the new schema. This also generates new starter dashboards that use the new schema. Remember to grant access to any teammates that need to query this new connection.

If you and your organization haven’t created any custom charts or dashboards, then you can delete the old Data Lake connections and starter dashboards from your Atlassian Analytics workspace.

If you have created custom charts and dashboards, continue reading for recommendations on how to migrate those charts and dashboards to the new schema.

Migrate custom charts

If you and your organization have created any custom charts or dashboards, do not delete the old Data Lake connections yet. Deleting an old Data Lake connection too early will permanently delete any charts that query it.

To migrate your custom charts to the new schema, you will need to edit each chart to use the new Data Lake connection.

Note: To resolve chart errors, you need permission to edit or manage the dashboard that the chart is on and permission to query the underlying data sources.

We recommend doing the following:

  1. If you haven’t already, create a new Data Lake connection.

  2. Determine which dashboards you want to migrate to the new schema.

  3. For each query in each chart, switch the data source to the new Data Lake connection.

    1. For visual mode queries, Atlassian Analytics automatically highlights any columns with errors.

    2. For SQL mode queries, you need to rerun the query to check for any resulting errors.

  4. Use the table in the next section called Schema changes to resolve any issues that come up after switching the data source.

  5. After you’ve migrated all your necessary dashboards, you can delete the old Data Lake connections. We also recommend deleting the dashboards you no longer need.

Schema changes

Table (old schema)


New schema

Jira Issue

Issue Number

The issue number is not available in the new schema.

You can instead use the Issue Key column in the Jira Issue table, which is the concatenation of a project key and the issue number. If you previously used the issue number together with the project key to derive the issue key, that derivation is no longer needed, and you can use the Issue Key column directly.

Jira Project


This field was renamed to Project Key.

Jira Project Category


The information in this table was incorporated into the new schema into the Jira Project table.

For example, instead of querying the Name column in Jira Project Category, you can now use the Project Category column in the new Jira Project table.

Jira Issue Affected Version mapping


This table was temporarily removed from the new schema and currently has no corresponding match in the new schema.

In Jira, issues can be linked to project versions—either through the Fix Version mapping or the Affected Version mapping. We're currently looking into ways to improve how Atlassian Analytics supports querying relationships between entities when multiple relationship types exist. On improving those capabilities, we will re-introduce the Affected Version mapping.

Jira Issue Priority

Jira Issue Status

Jira Issue Resolution

Jira Issue Type

Jira Issue Status Category

Name, Sort Order, or any other column

The information in those tables was incorporated into the new schema into the Jira Issue table. For example, instead of querying the Name column or the Sort Order column in the Jira Issue Priority table, you can query directly the columns Priority and Priority Sort Order, respectively, in the new Jira Issue table.

JSM CSAT Feedback

JSM Request type


The data for Jira Service Management CSAT feedback and Jira Service Management request type was incorporated into the new JSM Issue table. You can now use the corresponding columns in the new table.

Jira Issue Field

Jira Field Metadata

Jira Field Option


We’ve combined the information from these tables into a single Jira Issue Field table.

You can now use the corresponding fields in that new table instead of the columns that were in the old tables (for example, the Key, Name, and Type columns from the Jira Field Metadata table, or the Value column from the Jira Field Option table).

Other columns (notably Option Id and Option Ref from the Jira Field Option table) are not available in the new schema. Those fields were previously used to tie together data from the three original Field-related tables. With the new changes, those fields are now redundant. You can rewrite the query using only the new table. View an example below this table.

In addition, for Jira Service Management data, we introduced three new tables: JSM Issue (including Work category and Request type fields), JSM Change, and JSM Incident. Now you can access Jira Service Management fields directly from these tables, eliminating the need to query the Jira Issue Field table.

Example of editing a query that used the old Jira Field tables

In this example, the query previously tied together data from the Jira Issue Field, Jira field Metadata, and Jira Field Option tables: For a given Issue Id (defined in the Jira Issue Field table), it identifies a required field (using the Name column in Jira Field Metadata as a filter) and extracts the Value of that field from the Jira Field Option table.


With the new schema, this query can be simplified since all this information is available in a single table—the new Jira Issue Field table.


Search your queries

Use the Queries tab in the settings of your old Data Lake connection to search all queries that use a specific term such as a table or column name. By default, when you open this tab, Atlassian Analytics will show any queries with errors before you run any searches. This quickly surfaces any queries that need fixing.


For further assistance on how to migrate to the new Atlassian Data Lake schema, contact our technical support team by submitting a ticket and selecting Atlassian Analytics as the product.



Log in or Sign up to comment

Atlassian Community Events