Atlassian Analytics September Office Hours Recap

[#1]

Hi all,

Thank you to everyone who had time to join our office hour session last week. In case you missed it, here is a quick summary of a few questions asked during the session. We love getting to share tips and tricks on how to use Atlassian Analytics and the Atlassian Data Lake with you! If you have any specific features or questions you’d like to see covered in the next office hour session, don’t hesitate to leave a comment below!

👉  Remember to join our chapter on ace.atlassian.com to be notified of new Analytics office hour events.

-------------------------------------------------------------------------------------

Here are some of the questions and answers that came up during this round of office hours:

Q: When you want to share an Atlassian Analytics dashboard with stakeholders, do the stakeholders need an Atlassian Analytics license?

A: A stakeholder will need to be granted product access to Atlassian Analytics to be able to view a dashboard in Analytics, receive a dashboard subscription, or view a dashboard that is embedded using a Smart Link.

Q: Is there documentation explaining the different tables and columns available and what they correspond to in Jira?

A: Yes! Here is a link to our documentation on the schema of the Atlassian Data Lake. You can use the documentation to see a description of the data included in each table, view the definition of a column within a specific table, see the expected data type of a column, etc.

Note that the tables available in data shares will be different from those in Atlassian Data Lake connections in Atlassian Analytics. The definition of Jira tables in data shares is in the data share documentation.

Q: I have a few fields with checkboxes. I would like to report on how many Jira issues have all the checkboxes checked.

A: To query how many issues have all values of a Checkbox custom field selected on an issue, you’ll need to first figure out how many values can be selected in the field.

1. Add the “Value” column from the “Issue field” table to the query and use the “Count of unique” aggregation.

2. Add the “Name” column from the “Issue field” table as a filter and filter by the name of your custom field. For this example, we’ll filter by our custom field named ‘Customer segments’.

3. Run the query to see how many possible values can be selected in the checkboxes.

We can now see that the ‘Customer segments’ custom field has 3 values that can be selected in a checkbox. Next, let’s build on the previous query to see how many checkboxes are selected on our issues.

1. Add the “Issue key” column from the “Issue table” under the Jira family of products section of tables.

2. Run the query.

Optionally, you could add a “Filter” step to narrow down the results to any issues that had all 3 values of the ‘Customer segments’ custom field selected.

Q: If the same Jira custom field name is used across multiple sites, how can we be sure we’re querying the correct field?

A: In the Jira "Issue field" table, the “Field key” column will display a unique identifier such as ‘customfield_10140’. Since your custom fields have similar names, you can filter by the “Field key” column from the “Issue field” table instead of the “Name” column.

You can also use the “Workspace ID” column in the “Issue field” table and join it with the “URL” column in the “Workspace” table to check that you are bringing in the column from the desired site.

Q: What is the best way to stay updated on new functionality in Atlassian Analytics?
A: Our team announces newly released features in our Community group. We recommend watching our Community space if you aren’t already so you’ll be notified of new posts. If there’s a specific feature you’re interested in that has already been requested, we highly recommend watching the feature request ticket to know when it will be released.

Thanks again to everyone who joined us! As always, don’t hesitate to contact support for any assistance outside of office hours.