Skip to content

Deprecation of search enpoints #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
briavers opened this issue Mar 7, 2025 · 4 comments · May be fixed by #97
Open

Deprecation of search enpoints #91

briavers opened this issue Mar 7, 2025 · 4 comments · May be fixed by #97

Comments

@briavers
Copy link

briavers commented Mar 7, 2025

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

the /search endpoints will be removed as of may 1st Is there any plan for an update?

@herbdool
Copy link

The endpoints to use now are GET or POST of /rest/api/3/search/jql. I only just became aware of this so I'm scrambling for a replacement if this library doesn't yet support it.

@herbdool herbdool linked a pull request Apr 23, 2025 that will close this issue
@herbdool
Copy link

I created a PR which works for my use case: #97. It works with a simple JQL.

Might be useful to also implement the new bulk fetch: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-bulkfetch-post and the count api: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-approximate-count-post

@herbdool
Copy link

I ended up including the bulk fetch and count. It's working for me.

@herbdool
Copy link

In my testing using bulkFetch() has a significant performance improvement over get(), so I hope that it also gets merged in since the new search API won't return all the necessary fields (for our use case).

bulkFetch(): 0.04s per issue; get(): 0.4s per issue. So a ten times improvement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants