Issue Summary

This is reproducible on Data Center: (yes)

When a prior subtask is synchronized as a task to JA and its type is changed to "Story" in Jira, a new story is created in JA. Consequently, the original task is deleted from JA, resulting in only the newly created Story remaining.

However, in large instances with multiple connectors, some stories may end up sharing the same external ID. This situation prevents the deletion of the previously created task, which remains in JA and can be found under Items > Tasks as an orphaned item.

Steps to Reproduce

1. An issue is originally created as a Sub-task in Jira and thus synced over as a Task in Jira Align.
2. Subsequently, the issue was changed from a Sub-task to a Story, which triggered a new sync to Align, this time creating a Story in Align.
3. The original Jira is then updated with a new link to Align to this newly created Story.
4. The original Jira Align Task still lives on in an orphaned state in Align, with an active link back to the Jira issue.
5. When the user moves the Jira issue (now a story) to "Done", the sync to Align only updates the Story to "Completed", but the Task is still "Not started", as it is now, orphan

Expected Results

When fetching what tasks to delete, we should only check for stories that already exist on our current connector

Actual Results

JA is checking for stories on any connector, and when a match is found, it becomes unable to delete the task

Workaround

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