Jira and Confluence Cloud REST APIs · Endpoint removal
GET /rest/api/3/field/{}/context/defaultValue stops working
Stopped working
Calls to GET /rest/api/3/field/{}/context/defaultValue on Jira and Confluence Cloud REST APIs stopped working on October 1, 2026.
What to use instead of these calls
Move to the replacement custom field context default value API Atlassian announces under CHANGE-3082.
Atlassian's replacement API was announced as coming soon: someone must check it is available before migrating.
Calls it hits
GET /rest/api/3/field/{}/context/defaultValue
This API is deprecated and will be removed in October 2026. A replacement API that supports multiple default values per issue type within a context is coming soon.
Facts
- API
- Jira and Confluence Cloud REST APIs
*.atlassian.net - Kind
- Endpoint removal
- Takes effect
- October 1, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
More from Jira and Confluence Cloud REST APIs
- PUT /rest/api/3/field/{}/context/defaultValue stops working Stopped working
- GET /rest/api/3/workflow/search stops working Stopped working
- GET /rest/api/2/search is deprecated Deprecated, no date
- GET /rest/api/3/issue/createmeta is deprecated Deprecated, no date
- GET /rest/api/3/search is deprecated Deprecated, no date
- GET /rest/api/latest/search is deprecated Deprecated, no date