v2 is officially deprecated. This client is broken.

[droslean]

Are there any plans to update the client to use v3?

[droslean]

https://developer.atlassian.com/changelog/#CHANGE-2046

[droslean]

@andygrunwald Can you take a look? The client is broken now, since the v3 responses are different. V2 doesn't exist, it has been deprecated just today.

[danekantner]

Is this referencing the v2 search API? See: #715

[xino12]

+1
in a cloud instance we see:

Issue.Search {"Error": "The requested API has been removed. Please migrate to the /rest/api/3/search/jql API. A full migration guideline is available at https://developer.atlassian.com/changelog/#CHANGE-2046: request failed. Please analyze the request body for more details. Status code: 410"}

Well it's true using SearchV2JQL ti still works, sorry for the confusion

[droslean]

@danekantner Atlassian switched officially to v3. V2 is now deprecated. The client is completely broken. I stopped using it.

[andygrunwald]

@droslean, you are right that v3 is the latest version of the API.

Atlassian switched officially to v3. V2 is now deprecated.

Version 2 of the Atlassian Jira API is not deprecated. Can you point me to an official source which states this?
The documentation states:

Version
This documentation is for version 2 of the Jira Cloud platform REST API.

The latest version of the Jira Cloud platform REST API is version 3. Version 2 and 3 of the API offer the same collection of operations. However, version 3 provides support for the Atlassian Document Format(ADF).

Source: https://developer.atlassian.com/cloud/jira/platform/rest/v2/intro/#version

You are referencing https://developer.atlassian.com/changelog/#CHANGE-2046
This has been fixed in the current main version + v1 of this library. Please see #715 (comment)

The client is completely broken.

Can you state what is not working for you? I think a lot of people appreciate a bit more details, when such bold claims are made.

[cptlemons]

@andygrunwald the confusion is likely due to a temporary change made by Atlassian for their Jira Cloud product.

This morning sometime after 0800 UTC, the /rest/api/2/search/jql API on Jira Cloud instances started to return status 410 with the message:

The requested API has been removed. Please migrate to the /rest/api/3/search/jql API. A full migration guideline is available at https://developer.atlassian.com/changelog/#CHANGE-2046.

This was reverted around 1600 UTC and is currently working as it has before.

[andygrunwald]

@cptlemons Thanks for the notice and context. Is there a public reference for this? At https://jira-software.status.atlassian.com/ I am not able to see this incident.

[erikpeters-keap]

@andygrunwald I'm similarly not finding anything on the rollback for this, and we are still seeing this issue as well.
client.Issue.Search is returning the same message seen above

2025/09/17 20:53:12 failed to retrieve issues: The requested API has been removed. Please migrate to the /rest/api/3/search/jql API. A full migration guideline is available at https://developer.atlassian.com/changelog/#CHANGE-2046: request failed. Please analyze the request body for more details. Status code: 410

[cptlemons]

Our company had to open an internal support ticket to Atlassian when this change broke many of our services. Their response was to add our Jira Cloud instances "to the one time exception list till 30-September." Sorry I don't really have any useful information like versioning numbers or announcements.

[andygrunwald]

@erikpeters-keap @xino12 client.Issue.Search is deprecated, this is true. Your errors state. that you are still using Search(). Please have a look at #715 (comment) for your migration to IssueService.SearchV2JQL.

@cptlemons @droslean Are you refering to IssueService.SearchV2JQL() or client.Issue.Search()?

[droslean]

@andygrunwald It was for Issue.Search()... I am not sure if we had to migrate to SearchV2JQL, but this is not backwards compatible... I think it would be better to just leave the Issue.Search for v2 and create a new service for v3.. Either way, my team completely removed this client, or we implemented our own one with just the operations we need for our tools.

[erikpeters-keap]

Thanks @andygrunwald, migrating over to v2 was what I was missing - looks good now.
Appreciate the help

[knakul853]

seems like its broken again, we are getting this from last 2 days post migrating to SearchV2JQLWithContext

The requested API has been removed. Please migrate to the /rest/api/3/search/jql API. A full migration guideline is available at https://developer.atlassian.com/changelog/#CHANGE-2046

any plan to migrate to v3?

[andygrunwald]

@knakul853 It looks like you are still using the old Search() function? https://developer.atlassian.com/changelog/#CHANGE-2046 is not stating that /rest/api/2/search/jql is deprecated. Can you share

• your source code / a snippet
• the exact version of go-jira you are using

@ALL: Is there a plan to migrate this to v3? Yes. The question is only when, as this is a big undertaking and requires a lot of effort. I don't have a timeline for it.