Jira · Deprecation
Jira deprecation
Read from Jira's own page on 2026-11-09. 6 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.
Minimum notice
period: reasonable notice
Publicly accessibly REST APIs must be given reasonable notice of deprecations.Read from Jira's own page on 2026-11-09
Support window
period: at least 6 months
Any deprecated REST API in the cloud environment MUST be available in its original form for at least 6 months, with these exceptions:Read from Jira's own page on 2026-11-09
Announcement channels
channel: other
All effort should be taken to notify consumers, through all relevant communication channels of new deprecations.Read from Jira's own page on 2026-11-09
Deprecation / Sunset headers
deprecation: truesunset: true
Requests which are made to deprecated APIs SHOULD return a header on the response to notify the consumer that the endpoint is deprecated.Read from Jira's own page on 2026-11-09
Versioning scheme
Responses will not be tagged with the version of the API.Read from Jira's own page on 2026-11-09
Breaking change definition
An API is Backwards Compatible if a program written against one version of that API will continue to work the same way, without modification, against future versions of the API.Read from Jira's own page on 2026-11-09
Document
Download YAML · schema: API Commons Deprecation 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page