# Multiple contexts per project is coming soon **URL:** \ **Category:** Announcements\ **Tags:** jira-admin, jira-cloud-rest-api, jira-cloud, rest-api\ **Created:** [March 4, 2026, 10:29pm UTC](https://community.developer.atlassian.com/t/multiple-contexts-per-project-is-coming-soon/99432 "2026-03-04T22:29:00Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![JamesPetty](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@JamesPetty](https://community.developer.atlassian.com/u/JamesPetty)\ **Post date:** [March 4, 2026, 10:29pm UTC](https://community.developer.atlassian.com/t/multiple-contexts-per-project-is-coming-soon/99432/1 "2026-03-04T22:29:00Z")
> **Update October 2026:** > > Updated post with latest dates. API changes released in January 2027. Deprecated APIs will be removed in July 2027. > > See [Multiple field contexts per space is coming to Jira](https://community.atlassian.com/forums/discussion/3277838/multiple-field-contexts-per-space-is-coming-to-jira-join-the-early-access-program/p1#M3106) for information about the early access program. [CHANGE-3082](https://developer.atlassian.com/cloud/jira/platform/changelog/#CHANGE-3082) We’re introducing support for multiple field contexts per project. This is a [highly requested feature](https://jira.atlassian.com/browse/JRACLOUD-6851) which allows: 1. More than one context to exist for a single project across different issue types 2. More than one default value to be set for different issue types within a single context The existing REST APIs for managing context default values are no longer fit for purpose. The following APIs will be deprecated and replaced with new ones that support multiple default values for different issue types: - [Get custom field contexts default values](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-contexts/#api-rest-api-3-field-fieldid-context-defaultvalue-get) - [Set custom field contexts default values](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-contexts/#api-rest-api-3-field-fieldid-context-defaultvalue-put) ## Deprecation plan | Changes | Date | | --- | --- | | New default values REST API introduced supporting multiple contexts per project | January 2027 | | Changes to existing APIs: - Get custom field contexts default values will return an error when trying to read the default value from a context with multiple defaults - Set custom field contexts default values will populate the default value for all issue types on the context (this will override the default values set for specific issue types) | January 2027 | | Existing default values APIs removed | July 2027 | ## What you need to do If you use either of the above default values APIs, you’ll need to plan a migration to the new APIs before July 2027. The new APIs will support setting different default values for different issue types in a context. ---
**Author:** ![clouless](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/clouless/32/49469_2.png) [@clouless](https://community.developer.atlassian.com/u/clouless)\ **Post date:** [March 5, 2026, 6:53am UTC](https://community.developer.atlassian.com/t/multiple-contexts-per-project-is-coming-soon/99432/2 "2026-03-05T06:53:39Z")
Sounds great 🚀 Could you please also note that for some Marketplace Partners the missing DC← → Cloud mapping for contextIds is still a problem. And currently we have a workaround in our migration logic to map contexts from DC to Cloud by projectId. You can see more details here: [RFC-103: Jira Field Configuration Overhaul: Admin Experience and API Changes - #32 by clouless](https://community.developer.atlassian.com/t/rfc-103-jira-field-configuration-overhaul-admin-experience-and-api-changes/94205/32) thanks ---
**Author:** ![BenRomberg](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/benromberg/32/51777_2.png) [@BenRomberg](https://community.developer.atlassian.com/u/BenRomberg)\ **Post date:** [March 5, 2026, 2:12pm UTC](https://community.developer.atlassian.com/t/multiple-contexts-per-project-is-coming-soon/99432/3 "2026-03-05T14:12:33Z")
> [@JamesPetty](#): > > multiple field contexts per project @JamesPetty is there any way to try this out today? We’re not concerned about the changing APIs regarding default values, but have logic in our app that would need to be tested with multiple field contexts per project/space. ---
**Author:** ![system](https://global.discourse-cdn.com/atlassiandeveloper/original/3X/7/8/78672baa5ba80cd9164376457051d0eec038b082.png) [@system](https://community.developer.atlassian.com/u/system)\ **Post date:** [April 4, 2026, 2:12pm UTC](https://community.developer.atlassian.com/t/multiple-contexts-per-project-is-coming-soon/99432/4 "2026-04-04T14:12:44Z")
Closed on April 4, 2026, 2:12pm UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed. ---
**Author:** ![ianRagudo](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ianragudo/32/44527_2.png) [@ianRagudo](https://community.developer.atlassian.com/u/ianRagudo)\ **Post date:** [October 29, 2026, 7:44am UTC](https://community.developer.atlassian.com/t/multiple-contexts-per-project-is-coming-soon/99432/5 "2026-10-29T07:44:01Z")
Opened on October 29, 2026, 7:44am UTC