Issue Summary

When using the Built-in Jira Team field and configuring the Team mapping via API, Non-Standard UUID Formatted Atlassian Team will cause "Cannot create external team mapping. Incorrect data type for externalTeamId." Error

Steps to Reproduce

1. Find the Atlassian Team that has the UUID format of (8-4-4-4-12-1), six segments
2. It looks like the Advanced Roadmap Teams that are converted to Atlassian Team will have this format.
3. Example non-working Team ID: "ec79728c-49fa-4cbc-b4eb-5714b709ebb0-1"
4. Example working Team ID: "e21a0f92-4343-4c9f-b6f5-f0978b3ce069"
5. Follow the step here in this article and setup the Jira connector Team mapping

Expected Results

Team is mapped and received 201 Created response.

Actual Results

Error 400 Bad Request: "Cannot create external team mapping. Incorrect data type for externalTeamId."

The below exception is thrown in the c:\log\sitename-API-Date.log file:

Exception: AgileCraft.Repositories.Validators.Udal.ValidationException: The validation failed.
Incorrect data type for externalTeamId.
   at AgileCraft.Repositories.Validators.Udal.ValidationResult.ThrowIfInvalid() in C:\projects\alignapi\AgileCraft.Repositories\Validators\Udal\ValidationResult.cs:line 36

Workaround

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