Issue Summary

The following tables will have records that no longer exist in Jira: 

• jira_sla
• jira_issue_fix_version_mapping
• jira_issue_affected_version_mapping
• jira_issue_component_mapping
• jsm_affected_service
• jsm_incident_responder
• jsm_csat_feedback
• jira_issue_asset_object_mapping

This should only impact a very small percentage of customer data, and is not incorrect across all Data Lake connections.

Steps to Reproduce

Delete a version, project component, etc from Jira and it may not be reflected as such in the Atlassian Data Lake.

Expected Results

If a project component gets dissociated/removed from a Jira issue, it is expected that in the Atlassian Data Lake, the component no longer shows up as linked to the issue in the jira_issue_component_mapping table.

Actual Results

The project component may still show as associated to the Jira issue in the Atlassian Data Lake.

Workaround

None / manually filter out the incorrect data in a chart query