Learn how to add Atlassian Analytics to a site and understand what you need to query data and create charts.
Learn how to connect and manage your connected Atlassian data and external data.
Learn how to create insightful charts and dashboards with your organization’s data.
Learn how to use Visual SQL to create queries and transform data for making charts.
Need feedback on data? Learn how to share charts and dashboards with teammates so they can leave comments.
Learn how to grant resource access to the people who need it.
Learn how to manage your workspace and how to monitor your workspace activity.
If you make any changes to your original data source’s schema, you’ll want to sync your schema in Atlassian Analytics to make sure we have the latest version.
Keep in mind that Atlassian Analytics cannot automatically detect changes and sync your schemas.
You’ll need to manually sync the schema for any changes. Schema syncs are mandatory to use new tables in visual mode queries, but in SQL mode queries, you can query the new tables directly without having to update the schema if you know their SQL names.
To sync your schema:
You must have permission to manage the data source to sync its schemas.
Go to the Schema tab of the data source’s settings
Sync schema to sync the currently selected schema.
Sync all schemas if your data source has multiple schemas and you want to sync all of them.
After a successful schema sync, you’ll see a small summary showing how many changes were made to your Analytics schema.
Atlassian Analytics brings in all tables and columns it has access to and makes them visible by default. If you’d like to hide new tables and columns brought in from your schema syncs, select the Hide new tables checkbox in your data source’s general settings.
How renamed or removed columns affect visual mode queries
If we detect missing tables or columns in your actual data source are referenced in visual mode queries, you’ll see a warning section appear at the top of the page. Learn more about how to handle schema differences in your Atlassian Analytics queries.
Was this helpful?