Atlassian update - August 2024

Thank you for bringing to our attention the issue with the POST /rest/api/3/field/

/context/mapping endpoint not supporting Team Managed Projects (TMP) in Jira. We understand how this limitation can impact your workflow.

Currently, this endpoint is designed to work only with Company Managed Projects (CMP) due to the differences in how custom fields and contexts are managed between the two project types. While there are no immediate plans to extend this functionality to TMPs, your feedback is valuable, and I will forward it to our product team for consideration in future updates.

In the meantime, we recommend exploring alternative approaches for managing custom fields in TMPs, such as using project-specific configurations or leveraging other available APIs that support TMPs.

We appreciate your understanding and support. If you have any further questions or need assistance, please feel free to reach out.

Best regards,
Joe Nguyen
jnguyen2@atlassian.com
Product Manager - Jira Cloud

Endpoint POST /rest/api/3/field/{fieldID}/context/mapping is not supported by a Team Managed Project, it will only work with Company Managed Project

Steps to reproduce the behaviour on a TMP project:

1. Prepare Jira Cloud instance with developer canary program (install "developer assistant for Jira" from marketplace)
2. Create custom field type: single select which options
3. Create a team-managed project with an issue that has assigned a select custom field to the screen
4. set some option in this custom field
5. create request POST /rest/api/3/field/{fieldID]}/context/mapping (The Jira Cloud platform REST API) auth method - JWT token

RESULT

request returns the error message "These projects were not found: {projectID}"

This request is to have the endpoint behaving equally on both Company and Team managed projects.