Issue Summary

Using the ADO Connector, you must set the ExternalProject attribute to sync items created via the Align API.
However, using the Epic POST endpoint /align/api/2/Epics, the ExternalProject is not being set after submitting the API Call; it is set to the null value.
Hence, the item must be manually updated (Azure Devops AreaPath field) via UI in order to get synced to ADO.

It works with stories and Features

Steps to Reproduce

1. Have an ADO Connector properly configured to sync Epics
2. Now execute  Epic POST endpoint /align/api/2/Epics
   1. Make sure it has ConnectorID, ProgramID and,ExternalProjectID
3. Submit it
4. Note that both in Ui and in the response, the ExternalProject was set to null

Expected Results

The newly created API epic should have its external project set according to the payload and reflect in the Azure DevOps path in the UI.

Actual Results

After submission, the ExternalProject is set to null and the Azure Devops Area path is unassigned in the UI

...

Workaround

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