Jira Entity Properties Data Available on Analytics and Data Share

[#1]

Hi, community!

New Jira entity properties data is now available on Analytics and Data Share. These new tables expose key-value property data that apps, integrations, automations, and Jira use to store extra configuration or metadata on Jira entities, Jira Entity Properties. With these tables, you can query property keys and values directly from Analytics or Data Share.

The new tables will be rolled out gradually in the coming week.

The new tables

For Analytics, these 2 new tables are now available under ‘Jira Family of Apps’.

• ‘Project properties’. This table stores properties for Jira projects.

• ‘Work item properties’. This table stores properties for Jira work items.

Please make sure to toggle on ‘Show full schema’ in order to see the new tables.

             

For data share, the new table is 'jira_entity_property'. This table stores properties for a variety of Jira entities.

Key columns

The new property tables include a common set of columns to identify the property, connect it back to the Jira entity, and show the stored value.

For Analytics:

• Entity property ID - the unique identifier for the entity property, primary key.

• Property key - the name of the property. This can be user-defined for custom properties or set by Jira for internal properties.

• Value - the stored property value in string format. Values can be booleans, JSON, numbers, or strings.

• Version - the version of the property.

For Data Share:

• Entity type - show the type of entity the property is set on, such as 'IssueProperty' or 'ProjectProperty'.

How to get the new data

On Analytics, for all new Data Lake connections that include Jira data, the new tables will automatically be available. For existing Data Lake connections, an organization admin need to edit and save the connection to refresh the available schema.

On Data Share, the new table will automatically be available.

Send us your feedback

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

[Josh]

Thank you for the continued effort and attention to making this data available via the Data Share, @Tina Ling !

[Italo Lobato]

Can you share a KB explaining how to report JSM forms ? We would need to parse the stored property JSON?

https://jira.atlassian.com/browse/ANALYTICS-163

[Tina Ling]

Hi @Italo Lobato , 

To identify JSM forms, property_key will be 'proforma.forms.i#' or 'proforma.forms.p#'

To report on JSM forms content, you will need to parse out property JSON.  We are not sure yet on how everyone use JSM forms to come up with a clean parsing logic. But we will likely share a generic way of JSON parsing in community announcement soon. 

[Tina Ling]

Hi @Italo Lobato , 

To parse out non-nested JSON string, please reference this quick example for using both Visual sql and SQL mode.  Jira Forge Custom Fields on Analytics and Data Share

To see a more complete JSON parsing example, which include nested structure, please reference this Knowledge Base article.  https://support.atlassian.com/atlassian-analytics/kb/extract-values-from-a-json-string/