We’re introducing support for multiple field contexts per project. This is a highly requested feature which allows:
-
More than one context to exist for a single project across different issue types
-
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:
Deprecation plan
| Changes | Date |
|---|---|
| New default values REST API introduced supporting multiple contexts per project | July 2026 |
| 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) |
July 2026 |
| Existing default values APIs removed | October 2026 |
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 October 2026.
The new APIs will support setting different default values for different issue types in a context.
