Removing personal sandbox categories and ability to delete tables and columns from schemas

[#1]

Hi community,

Starting April 30, 2025, we’re making changes that will impact:

• personal sandbox categories

• deleting tables and columns in a schema

Read on for all the details on what’s changing and what actions you may need to take.

Removal of personal sandbox categories

To minimize the storage of personal data, we’re no longer going to automatically create personal sandbox categories for your dashboards. We'll consolidate all existing categories after we’ve migrated the dashboards accordingly.

Currently, when you create new dashboards, we automatically organize them into a nested category that uses your full name under “Sandbox” (for example, Sandbox > John Cloud).

When we roll out the changes, there will only be a single “Sandbox” category that will be shared across all users in your workspace. To do this, we’re going to:

• move all existing dashboards in nested sandbox categories (in other words, Sandbox > *) into the shared “Sandbox” category

• automatically organize all new dashboards into the shared “Sandbox” category

What you need to do

If you don’t want your dashboards in the affected nested categories to be moved into the shared “Sandbox” category, you’ll need to edit the categories of those dashboards. Any dashboards in categories that match the Sandbox > * pattern will be moved. Read more about how to edit dashboard categories.

Removal of the functionality to delete tables and columns in a schema

Note: This does not apply to custom tables and columns, which you’ll still be able to delete from schemas.

We’re removing this functionality for two reasons:

• It hasn’t worked as intended.

• It will help us prepare for supporting data residency in Atlassian Analytics.

Being able to delete tables and columns in an Analytics schema was meant to be a convenient way for users to hide tables or columns without modifying their original data source. But when you sync the schema, the tables and columns get added back if they still exist in your original data source. This means you’d need to delete them again every time you sync the schema.

We’re removing this functionality to reduce confusion and prevent potential problems that may happen from using it.

Our teams are also actively working toward supporting data residency in Atlassian Analytics. While we’d like to migrate everything, we’re prioritizing features that are most used and bring the most value to our customers. Removing the delete functionality will reduce the scope of the requirements and help us deliver support for data residency faster.

What you need to do

There are no actions to take for Atlassian Data Lake connections.

For Jira Align Enterprise Insights and third-party data sources, if there are tables or columns that you don’t want to bring in, you’ll need to alter the access of the database user you provide in your data source connection settings to grant it access to only the essential tables that are needed in Atlassian Analytics. You’ll need to refer to the documentation of the specific data source type to see if it supports these kinds of permissions.

When to expect these changes

We plan to roll out these changes starting April 30, 2025.

We appreciate your understanding. Comment below or contact support if you have any questions or concerns. Thanks!