Backend changes to improve data coverage in Jira Issue history table

[#1]

Hi community,

We want to let you know that we’re going to roll out major backend changes to a few Jira tables in the Atlassian Data Lake. These changes will enable us to improve the coverage of issue change events in Jira Issue History table, as well as fix an existing bug regarding missing data and ensure more accurate issue history records.

This backend change will happen to these tables:

In the Atlassian Analytics schema

• Issue history

• Issue status history

• Issue sprint history

• Issue cycle time

In the data shares schema

• jira_issue_history_change_item

Impact on usage

This change shouldn't impact how you query data. However, if you delete a custom field from your Jira instance, you may find data for the deleted custom field will stay in the tables longer. Currently, we are doing a weekly deletion of such deleted custom fields. After the change, the deletion action will happen less frequently.

If you notice anything unusual related to the affected Jira tables during the rollout period, please contact support to let us know.

Rollout schedule

The backend changes will happen gradually over a two week period, from Jan 20 - Jan 31.

Thank you for your patience and collaboration in this process.