-
Bug
-
Resolution: Fixed
-
Low
-
10.123.3
-
1
-
Severity 3 - Minor
-
No
Issue Summary
Connector custom fields teams can't be filtered on the projectKey and jiraTeamValue fields.
Steps to Reproduce
Use example requests:
- GET /Connectors/1/customFields/teams?expand=true&$filter=projectKey eq 'DEF4'
- GET /Connectors/1/customFields/teams?$filter=jiraTeamValue eq 'Colts'
Expected Results
We should be able to filter on these fields.
Actual Results
GET /Connectors/1/customFields/teams?$filter=projectKey eq null
GET /Connectors/1/customFields/teams?expand=true&$filter=projectKey eq 'DEF4'
400 Bad Request: Cannot get teamCustomFields with id 1. Could not find a property named 'projectKey' on type 'JiraCustomFields'.
GET /Connectors/1/customFields/teams?$filter=jiraTeamValue eq 'Colts'
400 Bad Request: Cannot get teamCustomFields with id 1. Could not find a property named 'jiraTeamValue' on type 'JiraCustomFields'.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available.
- is related to
-
JIRAALIGN-5369 Custom team mappings are being copied automatically when toggling the project dropdown to a project without existing mappings
- Closed
-
JIRAALIGN-5370 API: Can't create custom team mapping with null jira projectKey
- Closed
-
PS-141133 Loading...
- mentioned in
-
Page Loading...