Issue Summary

multi program features will cause this duplicate to happen in case one of the open Stories under it is linked to a different Project/Program. If we look at their logs, we will see the 2 API calls to create the Features, and we can notice that each one points to a different program.

Steps to Reproduce

1. Create a MultiProgram Feature on JA, and associate with at least 2 programs (each one linked to a project)
   1. one primary program, 2 additional programs, each with linked Jira projects
2. Add Stories under it, each one for a different program/project
   1. assign the corresponding Jira project to each story
3. Wait to sync with Jira
4. Close the stories that are on the same primary program as the feature
5. Leave the stories assigned to the addition programs of the Feature open
6. Split the feature
7. Wait for the sync to duplicate it

Expected Results

A duplicate Feature should not be created. When a Feature is Split, only the Feature Split1 having all closed/accepted Stories and Feature Split2 should have all the open Stories assigned to it.

Actual Results

A duplicate feature is created when a multi-program feature has an Open Story that is Split, while the Open Story is linked to a different Project/Program.

Workaround

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