/claim #2281
Adds a JiraServiceManagementConnector that indexes tickets from a specified JSM project (Service Request, Incident, Problem, Change, Service Task).
Rather than duplicating the existing JiraConnector logic, this PR implements JiraServiceManagementConnector as a thin subclass of JiraConnector, overriding only 3 hooks:
All checkpointing, authentication, pagination, slim docs, and incremental sync logic is inherited from the parent — zero duplication.
2 passed — ran: cd backend && python -m pytest tests/daily/connectors/jira_service_management/ -v
Closes #2281
Adds a JiraServiceManagementConnector to index Jira Service Management tickets with zero logic duplication by subclassing JiraConnector. Addresses Linear #2281 by meeting the requirement to ingest Service Request, Incident, Problem, Change, and Service Task issues.
New Features
JiraServiceManagementConnector with JSM issue type filter and DocumentSource.JIRA_SERVICE_MANAGEMENT.jira_service_management in the backend registry and source metadata; added UI config, credentials, autosync, and title handling.Refactors
JiraConnector now exposes overridable source, source_display_name, and jql_issue_type_filter; error and credential messages use display name, and process_jira_issue accepts source.onyx.connectors.onyx_jira for clean re-exports of JiraConnector and helpers.Written for commit f9ebf2b0d63cfe22753826ffce36f33c71c88ab0. Summary will update on new commits.
VasuBansal7576
@VasuBansal7576
Onyx (YC W24)
@onyx-dot-app