.png)
Connect Rippling to Jira Service Management so IT and HR service requests are automatically triggered by employee lifecycle events — with onboarding provisioning tasks, offboarding access revocation tickets, and agent access all driven from Rippling.
thePeopleStack configures the Rippling–Jira Service Management integration to convert employee lifecycle events into tracked, SLA-governed service desk workflows. New hire events create IT access and equipment provisioning requests routed to the correct agent queues; termination events create offboarding tickets that govern access revocation and equipment return with full audit trails. Agent access in JSM is provisioned from Rippling role data so IT and HR agents have the right queue access from their start date.
For clients using JSM for both IT and HR service delivery, we configure separate project queues and SLA policies for each function — ensuring IT service requests and HR case management each have appropriate routing, SLA targets, and agent access scoping driven by Rippling's department and role data.
Jira Service Management is deployed by thePeopleStack's Rippling clients primarily for US IT service desk and HR service delivery workflows, with agent queues, request types, and SLA configurations structured around US IT and HR operational requirements.
Canadian and cross-border operations: Canadian employees are provisioned into Jira Service Management as both agents and portal users through the same Rippling sync. thePeopleStack confirms that Atlassian data residency settings are addressed for cross-border service desk deployments where Canadian employee service requests and HR case data flow through Jira Service Management.
Jira Service Management is Atlassian's ITSM and service desk product — distinct from Jira Software (developer issue tracking). It handles IT help desk tickets, HR service requests, facilities requests, and change management workflows with SLA tracking and approval routing. The Rippling integration provisions JSM agents at hire, routes new hire onboarding requests through JSM, and triggers offboarding service requests at termination.
Yes. New hire events in Rippling can automatically create JSM service requests — IT access setup tickets, equipment procurement requests, facilities access provisioning — that route to the correct agent queues based on request type. This converts the Rippling onboarding trigger into a fully tracked, SLA-governed service desk workflow rather than an informal checklist.
Yes. Employee termination in Rippling can trigger a JSM offboarding service request that routes IT, HR, and facilities tasks to the correct agent queues with SLA governance. Access revocation confirmations, equipment return tracking, and final documentation steps each appear as ticketed, auditable tasks rather than ad hoc checklist items.
Yes. Rippling department and role data drives JSM agent license assignment and queue membership — ensuring IT agents, HR agents, and facilities agents each receive the correct JSM access on their start date. Non-agent employees receive JSM portal access for submitting requests without consuming an agent license.
A standard configuration covering SSO, agent provisioning, onboarding request automation, and offboarding request triggers typically takes 4–6 hours. JSM deployments with complex approval chains, many service catalog request types, or HR service desk configurations alongside IT service desk may require additional scoping.
