# Deprecation of override screen security **URL:** \ **Category:** Announcements\ **Tags:** jira-cloud, rest-api\ **Created:** [November 19, 2025, 10:56pm UTC](https://community.developer.atlassian.com/t/deprecation-of-override-screen-security/97153 "2025-11-19T22:56:36Z")\ **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:** [November 19, 2025, 10:56pm UTC](https://community.developer.atlassian.com/t/deprecation-of-override-screen-security/97153/1 "2025-11-19T22:56:36Z")
As announced in [Announcing project/fields association improvements for company-managed projects](https://community.developer.atlassian.com/t/announcing-project-fields-association-improvements-for-company-managed-projects/91653), the `overrideScreenSecurity` flag is being removed from the Jira REST APIs in early 2026. To minimise disruption caused by this breaking changes and to assist with migration away from the flag we’ve released changes to the [issue create](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post "https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post") and [issue edit](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-put "https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-put") APIs. They no longer require fields to be on a screen to be set including when not providing the `overrideScreenSecurity` flag, the fields do still need to be associated with the requested project + issue type. | Change | Date | | --- | --- | | Issue create and issue edit APIs no longer require fields to be on screen to be set | From October 2025 | | `overrideScreenSecurity` will have no effect on API requests | From January 2026 | ---
**Author:** ![KubaBialecki](https://avatars.discourse-cdn.com/v4/letter/k/ba8739/32.png) [@KubaBialecki](https://community.developer.atlassian.com/u/KubaBialecki)\ **Post date:** [December 15, 2025, 3:55am UTC](https://community.developer.atlassian.com/t/deprecation-of-override-screen-security/97153/2 "2025-12-15T03:55:51Z")
> [@JamesPetty](#): > > overrideScreenSecurity Hey! In the linked documentation referenced in the announcement, there is **no information** indicating that the `overrideScreenSecurity` flag will also be removed from the **Get edit issue metadata** endpoint: `GET /rest/api/3/issue/{issueIdOrKey}/editmeta` [https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-editmeta-get](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-editmeta-get) The announcement states that the flag is being removed from the Jira Cloud API. Could you please clarify whether this omission is intentional or a mistake? If the flag is indeed being removed from this endpoint as well, we want to express concern that this was not communicated earlier. This has a significant impact on our application, as we rely on this functionality to retrieve full metadata for fields that are not present on the issue’s edit screen. Losing this capability introduces a major functional limitation for our users. ---
**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:** [December 15, 2025, 1:34pm UTC](https://community.developer.atlassian.com/t/deprecation-of-override-screen-security/97153/3 "2025-12-15T13:34:22Z")
We share the same concern if it’s also being removed from `editmeta`. ---
**Author:** ![JamesPetty](https://avatars.discourse-cdn.com/v4/letter/j/dec6dc/32.png) [@JamesPetty](https://community.developer.atlassian.com/u/JamesPetty)\ **Post date:** [December 16, 2025, 2:20am UTC](https://community.developer.atlassian.com/t/deprecation-of-override-screen-security/97153/4 "2025-12-16T02:20:55Z")
Hi @KubaBialecki, thanks for raising this, let me clarify that for you. We won’t be removing `overrideScreenSecurity` from the get edit issue metadata endpoint. Understandably there could be consumers who are expecting this API to only return on screen fields when `overrideScreenSecurity` is not provided. Changing that behaviour to include all associated fields would not make sense in some use cases. Instead what we may do is include an alias for `overrideScreenSecurity` that provides a more meaningful name that better represents the behaviour of the flag, for example something like `includeAllAssociatedFields`. But the existing property will continue to work on that endpoint. ---
**Author:** ![system](https://global.discourse-cdn.com/atlassiandeveloper/original/3X/7/8/78672baa5ba80cd9164376457051d0eec038b082.png) [@system](https://community.developer.atlassian.com/u/system)\ **Post date:** [January 15, 2026, 2:21am UTC](https://community.developer.atlassian.com/t/deprecation-of-override-screen-security/97153/5 "2026-01-15T02:21:22Z")
Closed on January 15, 2026, 2:21am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.