Documentation Index

Fetch the complete documentation index at: https://docs.lansweeper.com/llms.txt

Use this file to discover all available pages before exploring further.

Jira Service Management Assets

Prev Next
Third-party tool information

We aim to provide accurate and helpful details about third-party tools, but we can't guarantee that this information is always complete or up to date. For the most reliable information, please always refer to the third-party tool's official documentation.

There are two ways to sync Lansweeper asset data into Assets in Jira Service Management: Assets Data Manager and the Lansweeper Marketplace app. Both bring Lansweeper inventory data into Jira Service Management, but they suit different starting points and goals.

Which option should I use?

Consideration Assets Data Manager Lansweeper Marketplace app
Best for Teams with existing object schemas, or teams that want to populate multiple schemas, including Atlassian's common data model schemas Teams with no existing schema who want to get started quickly
What it creates Reconciled Lansweeper data ready to import into any schema you choose A new, dedicated schema that mirrors your Lansweeper inventory structure
Plan required Service Collection Premium or Enterprise Service Collection Premium or Enterprise

Use Assets Data Manager if you already have object schemas to populate, or if you want to combine Lansweeper data with other sources across multiple schemas, including Atlassian's common data model schemas.

Use the Lansweeper Marketplace app if you have no existing schema and want to get set up quickly. It replicates your Lansweeper inventory structure in a new, dedicated schema.

Assets Data Manager

Assets Data Manager is a feature within Assets that connects, cleanses, and reconciles data from multiple sources, including Lansweeper, before you import it into a schema. Lansweeper is one of the supported adapters.

Prerequisites

  • A Service Collection Premium or Enterprise plan. Assets Data Manager is included in these plans.
  • Data Manager Adapters admin permissions. See Data Manager roles.
  • A Lansweeper Personal Access Token (PAT).

Connect Lansweeper to Assets Data Manager

Atlassian's adapter documentation covers the full setup. In outline:

  1. In Assets Data Manager, create a new job using the Lansweeper adapter.
  2. Select Cloud to Cloud as the fetch mode. The Lansweeper adapter shows a "Cloud enabled" indicator, so it runs on Atlassian's cloud infrastructure without a local client.
  3. Enter the job details: name, object class, data source name, and data source type.
  4. Generate a Lansweeper Personal Access Token (PAT) under Account settings > Developer tools > API clients > Create API client > Personal Access Token (PAT), then enter it in the job.
  5. Run the job to pull Lansweeper data into Data Manager as raw data.
  6. Map, cleanse, and reconcile the data using Data Manager's standard workflow.
  7. Save a search over the reconciled data, then import it into your object schema in Assets.

For the full setup procedure and field list, see Atlassian's documentation:

Lansweeper Marketplace app

The Lansweeper app for Assets in Jira Service Management fetches Lansweeper assets and syncs them directly into a new, dedicated object schema. You control the sync interval, filter which asset types sync, and choose which fields to bring across.

Features

Automated sync

  • Sync assets from Lansweeper and add them to Assets.
  • Set and control the sync interval.
  • Create new objects or update existing ones.

Filter asset types

  • View all asset types available from your Lansweeper site.
  • Turn syncing on or off per asset type.
  • Search for specific asset types.

Field configuration

  • Choose which fields sync from Lansweeper to Assets.
  • Add up to 30 fields, including existing ones.

Sync statistics

  • View the start time, end time, and status of each sync.

Prerequisites

  • A properly configured Jira Cloud instance.
  • A Premium or Enterprise plan for Service Collection and Jira Service Management. See Change your plan.
  • A Pro or Enterprise plan for Lansweeper. See Pricing & plans.
  • A Jira admin user.

Compatibility

Component Version/Details
Supported Browsers Google Chrome
Lansweeper REST API Version v2
Development Platform Atlassian Forge
Jira REST API Version v3
Forge CLI Version v10.6.1
Supported Lansweeper product Lansweeper Platform
App Hosting Type Cloud
Supported Products Jira Service Management

Install the app

  1. In your Jira Service Management account, go to Apps > Explore more apps.
  2. Search for Lansweeper App for Jira Service Management Assets.
  3. Select Lansweeper App for Jira Service Management Assets, then select Get it now.
  4. Wait for the installation to finish. A message confirms success.

If you don't see a success message, raise an Atlassian support ticket. Explain the issue and attach a screenshot.

Configure the app

Prepare credentials

Before you start, gather:

Verify your plan

Confirm your Jira Service Management cloud site has a Premium or Enterprise plan. If it doesn't, change your plan.

Connect Lansweeper and Atlassian

  1. In your Jira Service Management account, go to Apps > Manage your apps.
  2. Select Lansweeper App for Jira Service Management Assets Configuration.
  3. Select Allow access to let the app access Atlassian products on your behalf.
  4. Review the access request, then select Accept.
  5. Select the Connections tab.
  6. Enter your Lansweeper API URL and Lansweeper Personal Access Token under Lansweeper Credentials.

Create an object schema

We recommend creating a new object schema for the app.

  1. Open Assets in another browser tab.
  2. Select Create Schema.
  3. Select Create a blank schema.
  4. Complete the schema information fields.
  5. Select Create schema.
  6. In the object schema view, select Schema configuration, then the Roles tab.
  7. Add the Lansweeper app to the Object Schema Manager role.

Configure the import

  1. In the object schema view, select Schema configuration, then the Import tab.
  2. Select Create import.
  3. Select External Import as the import type, then select Next.
  4. Complete the import configuration fields.
  5. Select Create import.
  6. Select the three dots icon, then select Generate new token.
  7. Copy the Assets Import Token.

Complete the configuration

  1. Switch back to the app configuration tab.
  2. Under Atlassian Credentials, enter the Jira admin email address and Atlassian API token.
  3. Select Load Object Schema, then Continue to view the list.
  4. Select the blank schema you created (for example, Lansweeper Assets).
  5. Paste the Assets Import Token you generated.
  6. Under Scheduler Configuration, select an interval: hourly, daily, or weekly.
  7. Select Validate and Save.

Once you save the configuration, all fields on the page lock. You can only change them after you reset the configuration.

Filter asset types

After you connect the app, go to the Asset Types tab to turn asset type syncing on or off.

We recommend enabling only the asset types your service management use cases need. A focused schema improves the usability of your ITSM/ESM data. Use the search bar to find specific asset types.

Configure asset fields

Go to Apps > Manage your apps > Lansweeper App for Jira Service Management Assets Configuration > Asset Fields to view available fields. Some fields are required and can't be changed.

Edit or remove fields: delete the Jira Asset Field Name and its matching Lansweeper Field Name to remove a field. You can also edit the Jira Asset Field Name. Select Validate and Save to apply your changes.

Add new fields:

  1. Find the Lansweeper field name from the list of asset types.
  2. Select the field name to copy it.
  3. In the Asset Fields table, paste the field name into an empty row under Lansweeper Field Name.
  4. Enter a name under Jira Asset Field Name.
  5. Select Validate and Save.

Select Restore Default to revert to the default fields.

Custom asset fields: view custom fields on the related tab. Enable or disable each field to control whether it syncs. Use the search function if you have many custom fields.

Software and vulnerabilities

Under the Software/Vulnerabilities menu, you can enable two imports.

Software import: brings the list of software and versions into Assets from Lansweeper. Once imported, you can link back to the matching Lansweeper software record.

Vulnerabilities import: brings the list of vulnerabilities and their asset relations into Assets. Once imported, you can link back to the matching Lansweeper vulnerability record.

Data import

There are two ways to import data: a manual full sync and a scheduled sync.

Run full sync: after you complete configuration, the Run Full Sync button becomes active on the Connection tab. This updates the object schema and all assets.

Run a full sync the first time you use the app, and any time you change asset types, asset fields, custom asset fields, or software/vulnerability settings.

  1. Select Run Full Sync.
  2. A success message appears at the bottom left when the sync starts.

Scheduled sync: runs automatically at your chosen interval and performs a full data sync.

Check sync statistics

Go to Apps > Manage your apps > Lansweeper App for Jira Service Management Assets Configuration > Statistics to see the last five sync attempts, including start time, end time, and status.

View and manage assets

View assets

  1. In your Jira Service Management account, select Hardware. This shows all asset types imported from Lansweeper.
  2. Select an asset type to see its assets.
  3. Select an asset to view its details, including name, key, host site, and the Lansweeper Asset URL link back to Lansweeper.
  4. In Linked issues, view any Jira issues related to the asset.

View linked objects

  1. Go to Assets > Hardware, select an asset type, then select an asset.
  2. In Linked objects, view the outbound and inbound references and their relation types. Select an object link to go to that asset's page.

View object graph

  1. Go to Assets > Hardware, select an asset type, then select an asset.
  2. In Linked objects, select Object graph.
  3. Select an object link in the right pane to go to that object's graph.

Uninstall the app

  1. In your Jira Service Management account, go to Apps > Manage your apps.
  2. Select Lansweeper App for Jira Service Management Assets > Uninstall.
  3. Select Uninstall app in the confirmation dialog.

Troubleshooting

General issues: check the application logs.

  1. Log in to Atlassian Admin as a system administrator.
  2. Select Products > Sites and products.
  3. Select Connected Apps.
  4. Select the three dots, then Download logs.

Unable to install or activate the app: follow Installing Marketplace apps.

Permission errors: try one of these fixes.

Option 1: reinstall the app. Uninstall, then reinstall and reconfigure.

Option 2: revoke access.

  1. Go to Atlassian Admin and select your organization, if you have more than one.
  2. Select the site name and URL to open its admin area.
  3. Select Products, then the site from the left menu.
  4. Select Connected apps.
  5. Select Manage authorization for the app.
  6. Select Revoke access.
  7. Reload the configuration page.

If problems continue, contact Lansweeper Support.

Known behaviors

  • Configuration changes made after a sync starts don't affect that sync. They apply from the next sync.
  • Deleting assets in Lansweeper doesn't automatically remove them from Assets.
  • Resetting the configuration page during a running sync can cause that sync to fail.
  • If a sync fails unexpectedly, its status stays "in progress" for up to 24 hours, then resets automatically. You can also reset the configuration to restart it.
  • The app shows a maximum of 100 object schemas in the schema selector.
  • If ingestion fails partway through, the app retries up to 4 times, then marks the sync as failed.
  • Due to an Atlassian Jira limitation, you can't access user-side logs.
  • Renaming or adding a Jira asset field creates a new field in the current object schema. The change applies from the next sync cycle. It can also affect a sync that's currently running, because the checkpoint resets once the mapping change is validated and saved.
  • Refresh the page to see new asset types on the Asset Types tab.
  • Manually added assets stay as they are, unless they share an asset key with a Lansweeper asset already synced.
  • Deleted assets in Assets are recreated on the next scheduled sync, if the source asset still exists in Lansweeper.
  • If you edit a synced attribute in Assets, the next scheduled sync overwrites it with the Lansweeper value.
Build with the Lansweeper API

Lansweeper's APIs let you build apps that integrate with our IT discovery and inventory platform. See the Developer Portal to get started.