Top level record Epic (Feature) is automatically imported from the Jira integration when a user story from a different previously integrated Epic is added

What is the challenge?

We expect product managers to work the integration queue to import Epics (mapped to Aha! Features) from JIRA into Aha!, since Epics are the top level record in our mapped hierarchy. We do expect user stories (mapped to Aha! requirements) to import automatically as they map into Jira epics. The problem is that we have encountered a bug with the top level import logic, where Epics are automatically imported when a user story from a different mapped Epic is moved to the new Epic.

What is the impact?

This is undesirable for us, as we have trained all product managers to import Epics working the integration queue. There are some Epics they do not want to bring over to Aha! or are not ready to bring over, and this bug makes the overall behavior hard to bring and undoes intentional product manager decisions around what to bring over through the integration.

Describe your idea

Fix the bug so that the top level record is never automatically imported, regardless of the state of child records (known or unknown).