Issue Summary

When a Feature is split in JA, the Feature Split part 2 with Stories is created in Jira Align first. When the said Feature is assigned to a user, who's not added to the Jira project via Users & roles, thus not part of the permissions, the sync fails, and the Feature is not created in Jira. This leads to inconsistencies between the two systems as the new Feature is not created in Jira, and all Stories still continue to roll up to the old Feature, but in JA, the old Feature is marked as Done, and Stories that are not Done are now rolling up to Part 2 of the split Feature.

The underlying problem is that the JA API is attempting to create the issue in Jira and assign a user to the Feature simultaneously with one single API request. If there's an issue with the assignee, then the creation fails, and there's no way for the user to get alerted about this, as they think all is well.

Splitting the API calls to create Feature Part 2 and later adding the assignee would help with this problem, as it would create the work item on Jira and the Stories added to it correctly, only failing to have the correct assignee.

Steps to Reproduce

1. Create a Feature on JA
2. Create Stories under it
3. Mark some stories as Done
4. Let it sync to Jira
5. Now Split the Feature on JA
6. Assign the Feature Part 2 to a user that has no permission on Jira
7. See how the Stories continue to point to Feature Part 1 on Jira

Expected Results

The feature would be created without an assignee and stories rolled up to it correctly on Jira

Actual Results

The Feature Part 2 fails to be created on Jira, and the stories are rolled up to the incorrect Feature Part 1

Workaround

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