Looking for approaches that reduce manual work while keeping the process streamlined and auditable.

[Albie Sparv]

Right now, onboarding starts with a Jira Service Management request, but once it's approved, HR still has to jump into BambooHR, create the employee, enter all their details, coordinate with different teams, and keep track of everything manually.

It works, but as the company grows, it's becoming harder to manage, and it's easy for things to slip through the cracks.

We're hoping to automate more of this process while keeping everything visible and auditable.

Ideally, we'd like to be able to:

• Create a new employee in BambooHR automatically once a JSM request is approved.
• Populate employee information like Department, Manager, Job Title, Location, Start Date, and other relevant details.
• Let HR update employee information directly from JSM without needing to switch to BambooHR.
• Automatically create onboarding tasks for IT, HR, Admin, Documentation/LOI, and any other teams involved.
• Route those tasks to the appropriate teams automatically.
• Trigger onboarding activities such as laptop and account setup, policy acknowledgements, insurance enrollment, and employee notifications.
• Keep a complete audit trail showing who requested, approved, and completed each step.

I'm curious how others are solving this today.

• Are you using a Marketplace app, custom automation, or an integration platform?
• What's working well for you?
• Have you run into any limitations or lessons learned along the way?

Looking forward to hearing how other teams have approached this.

[Olga Cheban _TitanApps_]

Hi @Albie Sparv !

Managing onboarding across multiple systems like JSM and BambooHR can definitely get overwhelming as your team grows.

To handle the integration with BambooHR (creating employees and syncing data), most teams use Atlassian's native Automation for Jira combined with webhooks, or an external integration platform, such as Zapier.

The other piece is the onboarding coordination once the request is approved: IT, HR, Admin, and Documentation all doing their part in sync.

The most reliable way to handle this is to codify the full onboarding process once, so you never recreate the same tasks manually for each hire. In our team, we do this with our tools Smart Templates and Smart Checklist for Jira.

With Smart Templates, you save the whole onboarding structure as one reusable template. This includes a parent work item with child items for IT, HR, Admin, Documentation, and any other teams involved. Fields like department, manager, start date, and location are pre-filled through variables. When the JSM request is approved, Jira Automation can trigger and create the onboarding work items from your smart template in one go. Each subtask / child work item can be assigned to the right team automatically.

Smart Checklist adds the step-by-step actions inside each subtask. The IT one, for example, can include a checklist for laptop provisioning, account creation, email setup, and mandatory security policy acknowledgment. You can mark checklist items as mandatory, assign individual steps to responsible teammates, and set item-level deadlines. Smart Checklist also comes with its own native automation rules that auto-apply checklists to new work items based on your conditions, so this piece doesn't need to be wired up in Jira Automation separately.

Because the whole process happens inside Jira work items, the audit trail is there by default. Every change, comment, and status update is captured in the work item history.

Here is an example of an onboarding work item template that includes an epic with a set of tasks with checklists and variables:

And here's an example of a reusable onboarding checklist template:

I hope this helps!

[Harshit_miniOrange]

Hello @Albie Sparv ,

We've seen a similar challenge with a number of organizations. The request and approval process in Jira Service Management is usually straightforward, but the manual work that follows can quickly become difficult to manage as the business grows.

The biggest pain points tend to be provisioning access, coordinating tasks across different teams, tracking the status of each request, and maintaining a complete audit trail for compliance. Onboarding and offboarding are especially challenging because multiple applications, approvals, and teams are often involved.

One approach that has worked well is using Jira Service Management as the central request and approval portal, then automating the downstream actions such as user provisioning, task creation, notifications, and access revocation. This reduces manual effort while ensuring every action is tracked from request through completion.

If you're exploring Marketplace apps, we've built Identity Governance, Auditing & Access Control via JSM for exactly these kinds of workflows. It helps automate onboarding, offboarding, access requests, approvals, provisioning across connected applications, and provides a centralized audit trail for governance and compliance.

Out of curiosity, are you primarily looking to automate onboarding and offboarding, access requests, or the entire employee lifecycle?

We've seen a similar challenge with a number of organizations. While the request and approval process in Jira Service Management is usually straightforward, the manual provisioning and access management work that follows can quickly become difficult to manage as the business grows.

Thanks,
Harshit.

[James Anderson]

For us, creating the employee record in our HRMS isn't the hard part. The real challenge is coordinating IT, Admin, and other teams while keeping approvals, tasks, and audit trails in sync.

The employee lifecycle is another challenge. During onboarding, we need to ensure new hires receive the right accounts, devices, and resources on or before their first day, but occasionally things get delayed or overlooked. Offboarding is equally important. Revoking access promptly and recovering company assets can become difficult when multiple teams are involved, and we've occasionally found orphaned accounts or active access that wasn't removed on time.

I'm curious how others are handling this. Are using Jira Automation, custom integrations, or a Marketplace app to manage the entire process? I'd also love to hear what's worked well and any lessons you've learned.