mirror of
https://github.com/open-webui/oikb.git
synced 2026-11-05 01:27:25 +00:00
[GH-ISSUE #16] Jira connector uses a deprecated API #11
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/oikb#11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @expilu on GitHub (Jun 3, 2026).
Original GitHub issue: https://github.com/open-webui/oikb/issues/16
The connector fails with a 410 Gone. In the docker log:
open_webui_oikb | {"ts": "2026-06-03T11:05:04Z", "level": "INFO", "logger": "httpx", "msg": "HTTP Request: GET https://xxx.atlassian.net/rest/api/3/search?jql=project%3DXX&startAt=0&maxResults=100&fields=issuetype%2Cpriority%2Cdescription%2Cstatus%2Cassignee%2Cupdated%2Csummary \"HTTP/1.1 410 Gone\""} open_webui_oikb | {"ts": "2026-06-03T11:05:04Z", "level": "ERROR", "logger": "oikb.daemon", "msg": "Sync failed for jira:xxx: Client error '410 Gone' for url 'https://xxx.atlassian.net/rest/api/3/search?jql=project%3DXX&startAt=0&maxResults=100&fields=issuetype%2Cpriority%2Cdescription%2Cstatus%2Cassignee%2Cupdated%2Csummary'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410"}If I try to call the API directly that way with curl I get a more informative error:
{"errorMessages":["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"],"errors":{}}@expilu commented on GitHub (Jun 3, 2026):
The fix seems easy I created a PR #17
@jukakoski commented on GitHub (Jun 30, 2026):
PR #17 fixed the deprecated Jira search endpoint issue by switching from
/rest/api/3/searchto/rest/api/3/search/jql.However, this does not fully fix Jira sync for projects with more than 100 issues. The connector still used the old
startAt/totalpagination model, while the new Jira Cloud/rest/api/3/search/jqlendpoint usesnextPageTokenpagination.As a result, Jira sync only fetched the first 100 issues.
I opened a follow-up PR to fix the pagination here: #69