Upcoming removal of Jira Software tables

[#1]

What’s happening

We’re removing two tables from the Atlassian Data Lake schema: “Issue estimate history” and “Issue sprint history”. They have data inconsistencies that result in corrupt or missing data in certain cases and, therefore, do not meet the data quality bar that we’ve set.

Our team will continue to work on resolving these issues, and we plan to reintroduce these tables as soon as they meet our quality standards.

How to prepare

If possible, you should take steps to identify and edit any charts or controls that use columns from the affected tables.

If you have permission to manage an Atlassian Data Lake connection, you can get a list of queries using these tables by doing the following:

1. Select Data from the global navigation.

2. Select an Atlassian Data Lake connection from your list of data sources.

3. Go to the Queries tab of its data source settings.

4. Provide the table name that you’d like to search your queries for.

5. Optional: Select Download as CSV to save a local copy of the search results.

Learn more about how to search your queries.

When to expect these changes

We’re going to remove these tables in two weeks to give you time to edit your dashboards.

Once we’ve released the change, you may need to sync the schemas for your Data Lake connections to ensure they’re up to date. If you don’t sync the schemas, any remaining charts or controls that query the affected tables will display errors.

We understand the importance of this data. As mentioned earlier, we plan to reintroduce this data in a different form along with richer sprint data later this year.

Comment below or contact support if you have any questions or concerns about these changes. Thanks!

[Tracy Chow]

Update: This change is now live - any charts and queries querying the “Issue estimate history” or “Issue sprint history” tables will return errors.

Please sync the schemas for your Data Lake connections to ensure they’re up to date.