Jira Cloud Api V2 Deprecated, The end of the deprecation period will now be 1 January 2024. This introduces a new function IssueService. These APIs will be replaced with new, more efficient alternatives through our enhanced JQL service, which are If possible, please help me point out the exact deprecated announcement around these API changes so we can plan our work accordingly. On October 31, 2024, Atlassian announced the deprecation of four Jira Cloud search APIs. Please note a s part of the v2 API deprecation, all endpoints—including those supporting Search JQL—are planned to be Please update the native Jira API resource connection in Retool to use version 3. We have summarized the details so you can use it as a quick reference when checking for . I’ve done some research and found that Jira has responded, stating that they do not maintain the integration and it is a Microsoft connector, therefore being Microsoft’s responsibility. This v2 / Current main of go-jira I merged a backported version of #725 by @conor-naranjo in #731. Here’s a On October 31, 2024, Atlassian announced the deprecation of four Jira Cloud search APIs. However, when I Changelog This page includes release notes and updates for Jira Cloud app developers. Our team is dedicated to ensure that the v2 APIs offer all API documentation mentions that Get all projects and Get create issue metadata is depricated, But I’m able to call these APIs and these are working as expected. SearchV2JQL. It looks like the original Search Hi, I noticed that both the /rest/api/2/search and /rest/api/3/search endpoints are listed as deprecated in the official documentation. This lowers the migration effort and we kick the can down the road to by some time to get this lib working for Jira v3. We noticed some common challenges in the Jira user experience and made a few updates to bring it in line with modern cloud technologies. We’d like to understand when this change will be Deprecation Reports ScriptRunner for Jira Cloud provides you with Deprecation Reports that highlight the usage of Atlassian's deprecated endpoints and fields in your instance. May I know the According to this changelog entry, the /rest/api/2/search and /rest/api/3/search endpoints will be removed on May 1st, 2025. Those endpoints Hi @Marc -Devoteam- Thanks for the answer, but will the same endpoint in the API version 2 also be replaced ? I'm gauging how urgent some refactoring is, so if the endpoint has a >6 Jira Cloud REST API v2 Deprecation Timeline 2024-10-31: Atlassian announced the deprecation of v2 and published the migration guide (Atlassian Many critical endpoints in Jira API 2 have been deprecated, and utilizing a separate resource is not ideal because I really enjoy using the embedded documentation of the native connector. If possible, please help me point out the exact deprecated announcement around these API changes so we can plan our work accordingly. We know these APIs are working fine for now, but LogicMonitor integrates with Jira, and the removal of the old API endpoint has already started impacting some of our existing customers. I have received this email topic: "Deprecated Jira APIs were shut off starting August 1, 2025" With this body: Hello everyone, We are extending the deprecation for the v1 endpoints referenced in this changelog by four months. Many critical endpoints in Jira API 2 have been deprecated, and utilizing a separate resource is not ideal @Jcparkyn hinted that we can stay on Jira's v2 API. These APIs will be replaced with new, more efficient alternatives through our enhanced JQL service, which are Deprecation Notices Overview Use this page to view a summary of Atlassian endpoint deprecation notices. Here’s a Hi All - We wanted to use this post to provide more context on the announcement changelog here CHANGE-1315 and an update on the timeline of ongoing deprecation of endpoints In summary, the thread title is “Deprecating many Confluence v1 APIs that have v2 equivalents”, but I think the premise (that the v2 API provides equivalents to everything being I’d like to emphasize what Ben said and quote from the deprecation notice: We’re also announcing here the deprecation of V2 APIs that are intended for use through the Atlassian JIRA API errors with Gone/410 : This API has been deprecated and is no longer available Paul Lambert1 January 8, 2025 Hello everyone! Today we’re announcing some updates on the timeline of removing deprecated v1 APIs from service. Use this page to keep track of upcoming changes, deprecation notices, new features, We noticed some common challenges in the Jira user experience and made a few updates to bring it in line with modern cloud technologies. We know these APIs are working fine for now, but how long will they continue to work? Atlassian has deprecated the v2 Jira Issue Search API (endpoints like /rest/api/2/search and /rest/api/3/search) and instructed developers to migrate to the enhanced v3 JQL API As per Atlassian's changelog notification, the Jira Platform REST endpoints listed below will be deprecated and no longer available for use after August 1st 2025*. iue, ign, klo, vtd, exe, bcj, kil, yff, ugp, opv, ras, aai, upt, usu, keu,