Issue Summary

In the Jira Align (JA) user interface (UI) , it is possible to correct or modify existing Team Mappings  where no Jira Project is specified, this allows maintenance of the default team mapping settings in Jira Align. (under Manage Custom Fields)

Performing a modification  to an existing, default team mapping using the API (PATCH verb) is not possible.

API PATCH calls are successful at adjusting team mappings that are specific to a Jira Project

This bug relates to a previous bug for the POST command and creating new team mappings without a Jira Project - see https://jira.atlassian.com/browse/JIRAALIGN-5370

Steps to Reproduce

Make a PATCH request to custom team mappings, specific mapping ID  endpoint:

// PATCH /rest/align/api/2/Connectors/1/customFields/teams/<mapping ID>
[
  {
    "op": "replace",
    "path": "jiraTeamValue",
    "value": "New Jira Team",
    "projectKey": null
   }
] 

The mapping ID for the existing mapping  has to be found by using GET calls to /rest/align/api/2/Connectors/1/customfields/teams and can also be retrieved from Enterprise Insights.

Expected Results

Attempts to adjust jiraTeamValue, childTeamValue or teamId using PATCH should be successful and match what the UI can do. 

Actual Results

Error 404: Cannot update Connector id 1 with TeamCustomField id nnnn. ProjectKey not found.

Workaround

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