Adds a Jira Service Management (JSM) connector that pulls service desk tickets, requests, and SLAs.
/claim #2281
JiraServiceManagementConnector extends the existing JiraConnector, inheriting all checkpoint, poll, slim-doc, and permission-sync capabilities. It overrides _load_from_checkpoint to enrich documents with JSM-specific metadata:
customfield_10010)customfield_10020)customfield_10030)backend/onyx/configs/constants.py — Added JIRA_SERVICE_MANAGEMENT to DocumentSourcebackend/onyx/connectors/jira_service_management/ — New connector packagebackend/onyx/connectors/registry.py — Registered JSM connectorbackend/tests/daily/connectors/jira_service_management/ — 3 tests (source validation, JSM metadata fields, slim-doc consistency)updated >= (inherited)Fixes #2281
Adds a Jira Service Management connector that syncs service desk tickets and enriches them with request type and SLA metadata. Reuses the Jira connector pipeline for checkpoints, polling, slim docs, and permission sync.
New Features
JiraServiceManagementConnector (extends JiraConnector) with source DocumentSource.JIRA_SERVICE_MANAGEMENT.customfield_10010), time-to-first-response (customfield_10020), time-to-resolution (customfield_10030), and breach flags.Migration
jira_service_management when creating a connection and set project_key to a JSM project.jira_user_email, jira_api_token).Written for commit 976207b159b387e7373ac16f38b5f3bcadf745b7. Summary will update on new commits.
يوسف جمال يوسف محمد ناجي
@promisingcoder
Onyx (YC W24)
@onyx-dot-app