Rolling out "Major incident" and target date fields to Jira family and Jira Service Management table

[#1]

Hi, community!

We're bringing three more Jira issue fields into the Atlassian Data Lake:

• Major incident

• Target start

• Target end

We’ll gradually roll out these new fields over the coming 2 weeks.

Where to find these new fields

In Atlassian Analytics

"Is major incident" column and "Major incident' field

You’ll find a new Is major incident column in both the Incident and Issue tables under “Jira Service Management”. Having this column in two tables reduces the need to join with other larger tables.

Is major incident is a boolean column, it can be filtered by ‘true’ or ‘false’.

The Issue field table under “Jira family of products” will also have a new Major incident field name.

"Target start" and "Target end" fields

The Target start and Target end dates will show up as two new issue field types in the Issue field table under “Jira family of products”.

You can filter for them by using both the “Field type” and the “Name” columns with the following values in your queries:

• For target start:

  • Field type: com.atlassian.jpo:jpo-custom-field-baseline-start

  • Name: Target start

• For target end:

  • Field type: com.atlassian.jpo:jpo-custom-field-baseline-end

  • Name: Target end

The screenshot below uses the “Field type” column in the query filter and shows the corresponding field names for each field type.

In data shares

Data for the new fields are available in the jira_issue_field and jira_issue_field_metadata tables.

For each field, you can get the field value from jira_issue_field.value, but you’ll need to use a different filter for each field:

• Major incident:jira_issue_field.field_type_key = 'com.atlassian.jira.modules.servicemanagement.major-incident-entity:major-incident-entity-field-cftype'

• Target start: jira_issue_field_metadata.type = 'com.atlassian.jpo:jpo-custom-field-baseline-start' AND jira_issue_field_metadata.issue_field_id = jira_issue_field.field_id

• Target end: jira_issue_field_metadata.type = 'com.atlassian.jpo:jpo-custom-field-baseline-end' AND jira_issue_field_metadata.issue_field_id = jira_issue_field.field_id

How to get the new columns and issue fields

For existing Data Lake connections:

• An organization admin needs to edit the connections to add the new “Is major incident” columns. If the connection already includes Jira Service Management data, the organization admin can edit it and save it without making any changes. More about editing Data Lake connections.

• The data for the new Jira issue fields will automatically be available if the connection already includes Jira data. Otherwise, an organization admin will need to edit the connection to include Jira data.

For existing data shares, data for the new Jira issue fields will automatically be available.

Tell us what you think

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

[Josh]

Hi @Tina Ling

1. It's nice to see these fields being made available, especially since they're getting sent over through the data share as part of the initial release
2. The recent posts from the Analytics team regarding new field availability have been top notch:
   1. Very clearly communicated
   2. Helpful instructions and screenshots
   3. Timely notifications

Please keep up the great work!