A huge thanks to all who have provided feedback on Atlassian Analytics and the Atlassian Data Lake so far! Based on your feedback, we have been working on an improved version of the Atlassian Data Lake schema that will make it easier to query and build charts by reducing the need for complex joins and calculations. Improvements include but are not limited to:
New “Issue Key” column
More comprehensive Jira Issue and Jira Issue Field tables
New tables including Jira Issue Cycle Time, Jira Issue Status History, and other Jira Service Management-specific tables
This new schema will come in July. When we have a more precise date for its release, we’ll let you know as soon as possible.
When the new schema is released, all charts querying your existing Data Lake connections will break. For existing starter dashboards and Data Lake connections, the easiest path forward would be to delete the old data sources and create new ones. However, if you’ve created custom charts and dashboards, we will provide guidance on how to fix your existing chart queries. For end users who do not have edit access to charts, they will need to rely on the dashboard admins and editors to fix charts.
Given the incoming change, we recommend that you do not create many charts between now and the new schema’s release. So when the new schema comes, your business-critical dashboards may require less maintenance, and you can quickly get back to your usual workflows.
We know this schema update is disruptive to your work in Atlassian Analytics. For future schema iterations, we plan to provide better ways to maintain schema versioning and migration for your charts and dashboards. However, we do not expect breaking changes like this to occur frequently. These all feed into improvements our team is making to turn Atlassian Analytics and the Atlassian Data Lake into a more effective platform for our customers.
If you have any questions or concerns, please comment below.