Connect Claude & ChatGPT to Jira Service Management

26 tools for Jira Service Management

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

• add_customers_to_service_deskChanges dataGive existing customers access to a service desk by `service_desk_id` and their `account_ids`.
• add_request_commentVisible to othersAdd a comment to a request by `issue_id_or_key` with `body`. Set `public` false for an internal note; public comments are visible to and emailed to the customer.
• add_request_participantsVisible to othersAdd participants to a request by `issue_id_or_key` using their `account_ids`; they will receive notifications.
• add_users_to_organizationChanges dataAdd customers to an organization by `organization_id` and their `account_ids`.
• answer_approvalVisible to othersApprove or decline an approval on a request by `issue_id_or_key` and `approval_id` with `decision` approve or decline. Moves the request on and cannot be undone.
• create_customerChanges dataCreate a new customer account with `email` and `display_name`. Then add them to a service desk with add_customers_to_service_desk.
• create_organizationChanges dataCreate a customer organization with `name`.
• create_requestChanges dataRaise a new request on `service_desk_id` of `request_type_id`, with field values in `request_field_values` (e.g. summary, description). Use `raise_on_behalf_of` to raise it for a customer; they may be notified.
• get_organizationGet one customer organization by `company_id` (the organization ID).
• get_requestGet one customer request by `issue_id_or_key` (e.g. HELP-12), including summary, status, reporter and field values.
• get_request_slasGet the SLA timers of a request by `issue_id_or_key` (e.g. time to first response, time to resolution) and whether they are breached.
• get_request_status_historyGet the status history of a request by `issue_id_or_key` (each status and when it changed).
• get_request_type_fieldsGet the fields (required and optional) for a request type by `service_desk_id` and `request_type_id`, so you know what to fill when creating a request.
• list_organizationsList the customer organizations in Jira Service Management, optionally for one user by `account_id`.
• list_queue_requestsVisible to othersList the requests currently in a queue by `service_desk_id` and `queue_id`.
• list_queuesList the agent queues of a service desk by `service_desk_id`; set `include_count` for the number of requests in each.
• list_request_approvalsList the approvals on a request by `issue_id_or_key`, with approvers and decisions.
• list_request_commentsList the comments on a request by `issue_id_or_key`; filter with `public` or `internal`.
• list_request_participantsList the people who are participants on a request by `issue_id_or_key`.
• list_request_transitionsList the status changes you can make on a request by `issue_id_or_key` (e.g. Resolve, Cancel), with their transition IDs.
• list_request_typesList the request types customers can raise on a service desk by `service_desk_id`, optionally filtered by `search_query`. Needed before creating a request.
• list_requestsList customer requests you can see, filtered by `search_term`, `request_status` (OPEN_REQUESTS, CLOSED_REQUESTS, ALL_REQUESTS), `service_desk_id`, `request_type_id`, `organization_id` or `request_ownership`.
• list_service_desksList the service desks (help center projects) you can access, with their IDs and project keys.
• search_knowledge_baseSearch a service desk's knowledge base articles by `service_desk_id` and `query`. Set `highlight` to mark matching words.
• search_service_desk_customersList or search the customers of a service desk by `service_desk_id`, with optional `query` (name or email).
• transition_requestVisible to othersMove a request to a new status by `issue_id_or_key` and transition `id` (from list_request_transitions), with an optional `additional_comment`. The customer may be notified.

Questions