nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Effortless Employee HR data to JSM Assets Sync

Prabhu Palanisamy

Assets in Jira Service Management (JSM) offers powerful features to help organizations manage assets and configuration items (CIs) effectively. Having HR data such as employee information in Assets, offers significant benefits for your organization. In this blog post, we’ll explore the advantages of synchronizing employee data to Assets in Jira Service Management and provide a step-by-step guide on how to set it up using OnLink.

Benefits of Synchronizing Employee Data to JSM Assets

Using Employee Lookup Data in JSM Forms Without External API Calls

Synchronizing employee data with assets allows you to utilize this information directly in JSM forms without the need for external API calls. This means that you can easily access and reference employee data, such as names, titles, email addresses, and more, directly within JSM without additional integrations or complexities.

Jira Automation Approvals Using Employee Hierarchy

With employee data in sync, you can leverage Jira automation to streamline approval processes based on employee hierarchies. Whether it’s for incident resolution, change management, or other workflows, having access to an up-to-date employee hierarchy ensures that approvals are routed correctly and efficiently.

Employee Data as the Golden Record for Asset Associations

By maintaining accurate and synchronized employee data in Jira Service Management, you create a “golden record” that serves as a reliable source for associating additional assets. This ensures that your asset management is always up-to-date and reduces the risk of errors or discrepancies.

Getting Started with OnLink for Employee Data Synchronization

Now that you understand the benefits of synchronizing employee data with assets, let’s dive into the setup process using OnLink. Follow these steps to get started:

Access Schema Configuration in Jira Service Management
- Click on “Assets” within your Jira Service Management instance.
- Select the schema you want to import data into.
- Click on “Schema Configuration.”

Create an Import Using OnLink
- Within the Schema Configuration, click on “Import.”
- Choose “Create Import.”
- Select “OnLink Importer.”
- Give your import a name and click “Create Import.”

Configure Mapping Attributes
- Click on the three dots (ellipsis) and select “Configure app.”
- Set a name in the “Configure Mapping Attributes” popup.
- Click “Save Configuration.”

Access OnLink App Configuration
- Click again on “Configure app” to obtain a link that says, “To edit config use this link apps.”
- Click on the link to access the OnLink app configuration.
Edit Configuration
- Select “Edit” in the dropdown menu for the configuration you just created.
- Choose the “Source system” (currently limited to “Workday Custom Reports”).
- Select the “Report name” (username and report name combination, e.g., lmcniel/employee_data).
- Set the “Object type” to the specific object you want to map to.
- Map field-level attributes by matching Custom Report fields on the left with Schema attributes on the right. For example:
  - First_Name = Firstname
  - Last_Name = Lastname
  - Title = Title
  - Email = Email
  - Manager = Manager
  - HireDate = HireDate
  - DepartmentRef = DepartmentRef | RefID=${DepartmentRef}
  - Location = Location
  - Worker_ID = WorkerID
- Note: You can use AQL after the pipe symbol to map references to other schema attributes, as demonstrated in the mapping for “DepartmentRef.”
Testing the Setup
- To test the synchronization, go back to “Schema Configuration” in Assets.
- Click on “Import Data.”

Synchronizing employee data with assets in Jira Service Management using OnLink is effortless, from simplifying employee lookup to ensuring accurate asset associations. By following the step-by-step guide provided in this blog post, you can get started with OnLink and leverage these benefits to enhance your asset management processes. Stay ahead in your organization’s asset management journey and experience the efficiency and reliability of synchronized employee data in JSM Assets.

Comments

John Funk

Thanks for the article @Prabhu Palanisamy _Onward_

And just to clarify, currently OnLink only connects to Workday - correct? What other integrations are planned and when will those be coming?

Prabhu Palanisamy

Hi John, OnLink supports integrations to BambooHR, Paylocity, ADP Workforce Now, SAP SuccessFactors, Hi Bob, Darwinbox and Personio. You can also use the connector to import from Identity management providers e.g Azure AD, JumpCloud, Okta, Google Workspace. You can see the full list here.

On the roadmap for Q1 and Q2, we have Gusto, Namely, Netsuite, Paycor, UKG Ultimate Pro. You can see more details on our integrations landing page.

We also support generic mapping to a common HR canonical model. Using this you can import HR data from any system. In this case user has to map to the schema we provide.

Also, we support mapping to end systems asset data as well. e.g in this blog (there is demo video embedded in it), I explain how we can map to BambooHR's assets data.

Hope this helps.

John Funk

Awesome - yes, that's very helpful and very comprehensive! I am signed up for your upcoming webinar to see it in action.

Welcome!

It looks like you're new here. Sign in or register to get started.