You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Atlassian Analytics gives you access to the Atlassian Data Lake and powerful dashboard-building functionality. We believe the Data Lake will help you unlock additional value from your Atlassian products through easier and more complete access to data for reporting purposes. As we begin bringing our analytics capabilities to market, changes may still occur with our data and permissions model. Because of this, we recommend the following:
Do not rely on the Data Lake as a production-level data source yet
Only roll out Atlassian Analytics to a small group of people in your organization (and have them join this Community group to stay up-to-date on new features and changes).
When our analytics capabilities are released for General Availability (GA), that’s the time to share it with your whole organization.
The Data Lake is an Analytics data source. As such, connections do not reflect product permissions. Remember, whoever has access to a Data Lake connection can browse all the data scoped in that connection. During the early part of the EAP, we suggest you limit access to the Data Lake if you have sensitive data in there.
We welcome feedback from our open beta customers about the data model. Please be mindful that based on that feedback we may introduce breaking changes into the data model during open beta that may require you to update the queries or charts you have built to the revised schema. We will always post updates in this Community group, so that is the best place to keep updated on upcoming changes. Once we reach GA, breaking changes will be managed like changes to an API and will be done very sparingly.
Since our analytics capabilities are still in beta, you may find that certain fields or issues may not be up to date in the Data Lake. If you experience any inconsistencies between the data in the Data Lake and your Jira data, please notify our team as soon as possible so we address it.
We currently don’t support all custom field types in the Data Lake, but we’re working to add more over time. You can query your custom fields using the jira_issue_field table.
If your issue history data refers to deleted statuses, deleted issue types, or other information that is no longer available, this may result in null records for fields that could not be resolved, such as the status category for a deleted status. This can also affect derived fields like the issue cycle time. In the absence of status category data, you can use status information directly to calculate cycle time.
When you change an issue type for an issue and there's no request type associated with the updated issue, the data in the Data Lake may show an incorrect request type for that issue. To fix this problem, you'll need to enable the Default request type feature so a request type is always added whenever the issue type of an issue changes.
If you delete a Jira issue or project, for instance, the record will still show up in query results in Atlassian Analytics. We recognize this affects the data you see on your dashboards, so our team is looking to resolve this soon.
For example, Jira Software proprietary data such as field names and field values in German will not appear in German in the Data Lake, and when queried. Custom fields will, however, be in your language.
If you’ve identified an issue or limitation that’s not listed here, please raise it in the comments below!