Issue Summary

A Jira Epic is canceled on Jira Side, and then it is synced to the Jira Align and Enterprise Insights.

After this, going to the Enterprise Insights -> checking the table  [Story] column  [Fk Feature Id], the user sees that the current_dw is different from the export_dw.

The current_dw.[Fk Feature Id] = 0 and export_dw.[Fk Feature Id] = Feature_ID

Steps to Reproduce

1. Create a Jira Epic with Stories on Jira.
2. Sync it to the Jira Align.
3. Cancel the Jira Epic on Jira side.
4. Wait for the sync with Jira Align
5. Wait for the sync between Jira Align and Enterprise Insights.
6. Go to Enterprise Insights and check the schemas current_dw and export_dw on the Story table to check if the column [Fk Feature Id] is still linked to the canceled Feature.

Expected Results

Both schemas in the Enterprise Insights, current_dw and export_dw, register the column [FK Feature ID] = 0, on the Story table when a Jira Epic is canceled on Jira side, and it is synced with Jira Align and Enterprise Insights.

Actual Results

There is a discrepancy of data between current_dw.Story and export_dw.Story on the Enterprise Insights, when a Jira Epic is canceled on Jira side.

In the current_dw.Story, the column [FK Feature Id] is set as 0.

In the export_dw.Story, the column is [FK Feature Id] set as the Feature Id that was linked to the story when it was canceled on Jira Epic. 

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available