Issue Summary

This is reproducible on Data Center: (yes) / (no)

When a Jira Epic is canceled/removed in Jira it does not unassign the parent feature for a story in Jira Align's database correctly. This was result in the data in Enterprise Insights appearing incorrect.

See original JAC bug ticket opened for EI for more details and analysis: https://jira.atlassian.com/browse/JIRAALIGN-5267

Steps to Reproduce

1. Create a Jira Epic with Stories on Jira.
2. Sync it to the Jira Align.
3. Cancel/deted the Jira Epic on Jira side.
4. Wait for the sync with Jira Align
5. Open the story slide out and see the feature is still assigned to the story
6. Query the story table in the Jira Align DB and view the feature ID column

Expected Results

Parent feature field is unassigned in Story slide out and feature ID column in story table in Jira Align DB reflects as unassigned.

After review by the development team, the behavior is working as expected. The expected result is that Canceled/deleted parent feature still shows as assigned to the story in the UI and Jira Align DB.

Actual Results

Canceled/deleted parent feature still shows as assigned to the story in the UI and Jira Align DB.

...

Workaround

Alter their Cancellation flow in Jira Software, by adding either a Post Function or using Automation for Jira to write a rule to disassociate all child issues from the parent when the parent is moved to Cancelled. Those updates would then flow over to JA since the parent/child relationship has been broken.