Get request type fields
Inspect field IDs, required fields and allowed values before creating a request.
Connector library
Jira Service Management connector.
Create and track Jira Service Management Cloud requests, inspect required fields, add comments and perform available transitions.
Connector download
Download Jira Service Management
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.1 Choose version
- Release
- 2026-10-03
- Package
- Implemented source
- Schema credentials
- Basic auth
- Connection settings
- API Base URL
- Package size
- 9 KB
- SHA-256
eaba6adb36c351a396fc83254c1b3cc8dbcbe18f4b058f099660bb4a4357c4d8
Version history
What's new
- v0.2.0.1Latest · 2026-10-03 · Implemented source
Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.
- v0.2.0.0Earlier · 2026-10-02 · Implemented source
Replaces generic HTTP scaffolding with explicit vendor actions and selected credentials.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Historical package retained unchanged from repository commit f23d25b3ea418842aeabdc0e7bd91d97167da66b.
Included in this version
Included actions
Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.
Create request
Create a Jira Service Management Cloud request with request-type-specific fields.
Get request
Read the request identity and current status.
Add request comment
Add a comment with explicit public or internal visibility.
Get request transitions
Read one bounded page of available request transitions.
Transition request
Perform an available request transition; use Get request to confirm the resulting status.
Vendor API
API and access
Implementation considerations
- Support APIs often distinguish agent/admin operations from end-user request operations; confirm the right permission model.
- Keep requester identity, organization, assignee, status, and external IDs mapped explicitly.
- Use ticket events for updates, but protect against loops when CXFabric writes back to the same system.
Related connectors
More in CX & Support APIs
Support
Need help with Jira Service Management?
Tell us what you need to connect or change.