Implemented a new connector for Jira Service Management. This allows Onyx to pull tickets directly from Jira projects. I have followed the official connector guidelines and integrated the Jira API logic. Claiming Bounty: /claim #2281
Created a test Jira Service Management instance. Verified that tickets are being fetched correctly. Confirmed that environment variables for API keys are working.
Description: Implemented a new connector for Jira Service Management as requested. This follows the standard connector architecture. Claim Bounty: /claim #2281 How Has This Been Tested? Verified fetching tickets from a test Jira Service Management project. Demo Video . [https://www.loom.com/share/50204356b3904491aacfa445c17281fd]
Adds a Jira Service Management connector to index tickets with project/epic hierarchy and permission sync, plus slim-doc support. Uses Cloud enhanced JQL ID prefetch + bulk fetch with Server/DC v2 fallback, and adds safety checks and clearer error handling; addresses #2281.
New Features
ExternalAccess, with indexing-time prefixing and per-project caching.nextPageToken, offsets) and handling for 400/401/403/429; 1‑hour backoff for date-boundary quirks.JSM; slim sync batch size controlled by JSM_SLIM_PAGE_SIZE.Migration
jsm_user_email, jsm_api_token; optionally project_key or jql_query.api.atlassian.net, links use your instance base).labels_to_skip, comment_email_blacklist, batch_size, JSM_CONNECTOR_MAX_TICKET_SIZE, JSM_CONNECTOR_LABELS_TO_SKIP, JSM_SLIM_PAGE_SIZE.Written for commit 4242af0246e8ee731f0e8826b0de81c4098a798b. Summary will update on new commits.
Abubakar sabir
@abubakarsabir924-cell
Onyx (YC W24)
@onyx-dot-app