Upcoming Deprecation of Jira Cloud Search APIs

[glewandowski]

Is your feature request related to a problem? Please describe.
On October 31, 2024, Atlassian announced the deprecation of four Jira Cloud search APIs. These APIs will be replaced with new, more efficient alternatives through our enhanced JQL service, which are currently available for use. You can read more about these new APIs here.
Effective May 1, 2025, Atlassian will remove the following Jira REST endpoints:

• GET /rest/api/3/search
• POST /rest/api/3/search
• POST /rest/api/3/search/id
• POST /rest/api/3/expression/eval
  We have identified that this library may be used to access the deprecated endpoints in Jira Cloud. Failing to migrate to the new APIs before May 1, 2025, could negatively impact any solutions that depend on this library. By evolving our JQL service, we aim to provide a more reliable, performant, and scalable Jira experience tailored to meet the needs of enterprise customers.
  If you have any questions or require further assistance, please do not hesitate to ask on our developer community forum

Describe the solution you'd like

jira-ruby/lib/jira/resource/issue.rb

Line 51 in afef22a

def self.jql(client, jql, options = { fields: nil, start_at: nil, max_results: nil, expand: nil,

should be updated to new url /rest/api/3/search/jql. Also, the functions exposes some options which are not available in new API. Example:

• startAt which was replaced with nextPageToken
• validate_query which is not available at all

Describe alternatives you've considered
N/A

Additional context
N/A

[robotfelix]

Just to update this issue, it seems like Atlassian has followed through with turning off these JIRA APIs in the past 1-2 days ago.

Trying to search issues using JQL now results in a JIRA::HTTPError: Gone error for us.

[drvn-mr]

The issue search with JQL is gone for us as well.
It's trivial to update for non-paginated use cases, mostly switching the default fields to ["*navigable"].

[freibuis]

just hit us today.

what were the changes that you guys are propsing?

change the default rest_base_path => /rest/api/3
is that all that is need to be done. ?

[freibuis]

I have created a PR to fix this and make this method work better with paging support

#467

[drewish]

Yeah started hitting these Gone errors today. Also realized that the gem has an undocumented dependency on ActiveSupport:

/Users/amorton/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/jira-ruby-2.3.0/lib/jira/http_error.rb:11:in `initialize': undefined method `presence' for "Gone":String (NoMethodError)

      @message = response.try(:message).presence || response.try(:body)
                                       ^^^^^^^^^
Did you mean?  presence_in
        from /Users/amorton/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/jira-ruby-2.3.0/lib/jira/request_client.rb:13:in `exception'
        from /Users/amorton/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/jira-ruby-2.3.0/lib/jira/request_client.rb:13:in `raise'
        from /Users/amorton/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/jira-ruby-2.3.0/lib/jira/request_client.rb:13:in `request'

[ashkulz]

See this temporary solution.