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 and issue edit 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
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:
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.
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.