Issue Summary
When performing a request for the Get custom field context using the fieldId parameter with a custom field that contains scope, the REST API response returns an error that the custom field was not found.
Steps to Reproduce
- Access a Team managed project, and go to the project settings.
- Go to the issue type, and create a custom field (which will have the scope of the project).
- Find the custom field with the following endpoint: Get fields.
- Search for the custom field context using the fieldId with the ID of the custom field that was created and has the scope: Get custom field context.
Expected Results
The context result.
Actual Results
The below response is returned:
{ "errorMessages": [ "The custom field was not found." ], "errors": {} }
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
JRACLOUD-80743 /context/mapping REST endpoint does not work on Team Managed Project
- Closed
-
JRACLOUD-81481 Support for creating App project-scoped custom field types in team-managed projects
- Closed