Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Forge Custom Fields on Analytics and Data Share + Columns Deprecation Reminder

Hi, community!

Jira Forge custom fields data is now available on Analytics and data share. Forge custom fields are special types of custom fields created by Forge apps. These fields are added to Jira work items via the Jira Forge platform.

The new data will be rolled out gradually in the coming 2-3 weeks.

 

Where to find Forge custom fields data?

Forge custom fields will be stored together with all other Jira work item custom fields. They are just new row records in the existing Jira field table, one row per field.

For Analytics, the new fields will be available in ‘Work item field’ and ‘Work item custom fields’ tables under ‘Jira Family of Apps’ schema.

For data share, the new fields will be available in jira_issue_field table.

 

How to identify Forge custom fields?

For all the Forge custom fields records, ‘Field type' column value will be "com.atlassian.forge:field". Other than this, they will appear the same way as all the other work item fields, with the value in the 'Value’ column.

If you are look for parsing out a few field values, here’s how to do it using Visual SQL:

              Screenshot 2026-06-18 at 3.19.07 PM.png

If you are looking for processing more values in one statement, here’s a generic example using SQL:

SELECT
issue_id,
field_key,
name AS field_name,
field_type,
get_json_object(value, '$.type') AS forge_type,
CASE get_json_object(value, '$.type')
WHEN 'STRING' THEN get_json_object(value, '$.string_value')
WHEN 'NUMBER' THEN get_json_object(value, '$.number_value')
WHEN 'USER' THEN get_json_object(value, '$.user_value')
WHEN 'GROUP' THEN get_json_object(value, '$.group_value')
WHEN 'MULTI_STRING' THEN get_json_object(value, '$.multi_string_value')
WHEN 'MULTI_USER' THEN get_json_object(value, '$.multi_user_value')
WHEN 'MULTI_GROUP' THEN get_json_object(value, '$.multi_group_value')
WHEN 'OBJECT' THEN get_json_object(value, '$.object_value')
WHEN 'DATE' THEN get_json_object(value, '$.date_value')
WHEN 'DATETIME' THEN get_json_object(value, '$.datetime_value')
END AS parsed_value
FROM jira_issue_field
WHERE field_type = 'com.atlassian.forge:field'
AND value IS NOT NULL
;

Upcoming columns deprecation - 3rd notice

On July 6th 2026, these 2 columns will be removed. Please make sure your charts, dashboards or filters no long contains these columns.

  • Team “Scope mode” in Analytics, atlassian_team.scope_modefor Data Share

  • Team member “Role” in Analytics, atlassian_team_member.role for Data Share

Please refer to our earlier announcement for details. https://community.atlassian.com/forums/Atlassian-Analytics-articles/Upcoming-columns-deprecation-and-value-change/ba-p/3219636

How to get the new data

For both Analytics data lake connection and data share that include Jira data, the new records will automatically be available.

When the columns are removed, the changes will automatically be reflected in your lake connection. If you have existing chart or dashboard containing these columns, there will be an error message on the top of the lake connection page. Please modify the charts or dashboards.

Send us your feedback

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

 

 

 

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events