/claim #2281

Implemented a new connector for Jira Service Management (JSM).

Key Changes:

• Created JSMConnector using the dedicated JSM REST API endpoint (/rest/servicedeskapi/request).
• Mapped JSM customer requests to Onyx Section models.
• Included metadata for ticket status and request IDs.

This fulfills the requirement for a separate JSM-specific connector as discussed in the issue.

Summary by cubic

Adds a Jira Service Management connector that fetches requests from /rest/servicedeskapi/request and indexes them for search. Completes #2281 with a JSM-specific integration separate from Jira Cloud.

• New Features

  • Onyx: JSM connector returns Sections with a web link, “Ticket: summary + description” content, and metadata (status, request_id, connector_type: jsm).
  • Danswer: JSM connector implements PollConnector with load_credentials(email, api_token), basic auth, 30s timeout, 50-item pagination (respects isLastPage), and start/end filtering via createdDate.epochMillis. Emits Document batches (DocumentSource.JIRA) with id jsm_{issueId}, a linked “Summary + Description” section, and semantic_identifier=summary. Skips items without issueId and logs then re-raises on fetch errors. Uses SecondsSinceUnixEpoch in poll_source.

• Bug Fixes

  • Fixed package path: removed stray backend/damswer/connectors/jsm/__init__.py and added backend/danswer/connectors/jsm/__init__.py.

^{Written for commit c47338d80f4b52fa49465727f7713b0453bb4f30. Summary will update on new commits.}