Jira Service Management integrations

Jira Service Management integrations

→

AFAS Profit → Jira Service Management

AFAS Jira Service Management integration: customers, Assets and onboarding requests from AFAS Profit

→

Workday → Jira Service Management

Workday Jira Service Management integration: customers, organizations and onboarding requests from Workday

→

Visma Raet YouForce → Jira Service Management

YouForce Jira Service Management integration: employees, teams and onboarding requests from Visma Raet

→

HiBob → Jira Service Management

HiBob to Jira Service Management integration: onboarding, offboarding and change requests from Bob

→

HR2day → Jira Service Management

HR2day to Jira Service Management integration: customers, organizations and onboarding requests per employment relationship

→

Personio → Jira Service Management

Personio Jira Service Management integration: new colleagues in the portal and onboarding requests before they start

Systems you can connect Jira Service Management with

How KoppelHet connects to Jira Service Management

Jira Service Management Cloud REST API under /rest/servicedeskapi/ for customers, organizations, service desks, request types and requests. Agent accounts run through Atlassian's User provisioning API (SCIM).

Authentication: Basic authentication met API-token, of OAuth 2.0 (3LO) voor apps van derden

Objects we connect

• Customers and organizations
• Requests and request types, including onboarding and offboarding
• Managed accounts through SCIM

What a Jira Service Management integration does

• HiBob, Personio, Workday → to Jira Service Management

  Employees as service desk customers

  New employees from HiBob, Personio or Workday become Jira Service Management customers and members of their department's organization.

  HiBob → Jira Service Management integrationPersonio → Jira Service Management integrationWorkday → Jira Service Management integrationHR to ITSM

• Personio, Workday, AFAS Profit → to Jira Service Management

  Onboarding request for a new colleague

  A hire creates a request of the onboarding request type through POST /rest/servicedeskapi/request, on behalf of the new employee (raiseOnBehalfOf), with start date, job and manager in the fields. A departure results in an offboarding request.

  Personio → Jira Service Management integrationWorkday → Jira Service Management integrationAFAS Profit → Jira Service Management integrationHR to ITSM

• Microsoft Entra ID, Okta → to Jira Service Management

  Agents and Jira users through SCIM

  Agent accounts run through Atlassian's User provisioning API. On leaving the integration deactivates the managed account.

  Microsoft Entra ID integrationsOkta integrationsIdentity and access management

What to watch for

• Organizations group customers. We use them for department or entity from HR, so a team sees each other's requests where that is configured.

In your IT landscape

• Runs as a managed integration on the KoppelHet platform, next to your existing integration layer. No VPN into your network.
• Only the fields in the design you approve are transferred. The platform keeps no register of its own.
• Tested first in the test or acceptance environment where there is one. You choose the go-live moment.
• ISO 27001 certified, hosted in Amsterdam. When the contract ends you receive the configuration and the audit logs.

Implementation, architecture and compliance

Processes with this system

• HR to ITSM

Topics that involve Jira Service Management

• People and departments
• Onboarding and offboarding tickets

Articles about Jira Service Management

• Onboarding tickets from HR: when, what goes in, no duplicates
• Keeping people in the service desk current without Excel imports