Skip to:

Marketplace

Data Manager Clients for JSM Assets

works with Jira Cloud
Get it now

Free app

OVERALL RATINGS

DOWNLOADS

2,318

SUPPORT

  • Partner Supported

Showing details for Cloud

Key highlights of the appGet these tools to get started with Assets Data Manager

Supporting media

More details

The Data Manager Clients for JSM Assets are locally-installed middleware clients that run on the command line.

  • The Assets Adapters Client is required to move data from your tools, databases, and files into Assets Data Manager.
  • The Assets Cleanse and Import Client is recommended to Cleanse and Import data from your data sources using the command line.

The Data Manager Clients for JSM Assets are available for a wide variety of operating systems and architectures.
Learn about the system requirements of these tools.

Configure your settings in Assets Data Manager before you run the Data Manager Clients for JSM Assets.
Learn more about setting up Assets Data Manager.

Resources

  • Download

    Get the .jar file downloaded to your system

  • App documentation

    Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy and security questionnaire has not been filled by the partner

Privacy policy

Atlassian's privacy policy is applicable to the use of this app.

Atlassian privacy policy

Security program

This app is part of the Marketplace Bug Bounty program.

About Bug Bounty program

Version information

Version 2.0.4•for Jira Cloud

Release date
Sep 10th 2026
Summary
Lansweeper software inventory import and additional hardware attributes.
Details

New Features

  • Lansweeper Software data type : The Lansweeper adapter can now import software inventory in addition to hardware assets. Select the Data Type in your Lansweeper configuration - Hardware (the default) or Software. When Software is selected, the adapter pages through grouped software records from the Lansweeper GraphQL API and imports 14 fields: Software, Publisher, Type, Category, UNSPSC, Languages, Editions, Architectures, Versions, InstallType, InstallDate, RelatedSoftwareNames, OperatingSystems and Assets. The multi-value fields (Versions, Editions, Languages, Architectures, OperatingSystems and RelatedSoftwareNames) are imported as comma-delimited values in a single column; a list too long for the column is cut at a value boundary and ends with ... so no value is split part way through. Existing Lansweeper configurations default to Hardware and continue to work unchanged.

Improvements

  • Lansweeper adapter - additional hardware asset attributes : The Lansweeper adapter now imports Url (a link back to the asset record in Lansweeper), SubType (device routing and chassis type, such as laptop, desktop or server), ScannerType (the scanner that discovered the asset, for example Intune, SCCM or AssetRadar) and the cloud attributes CloudProvider, CloudResourceId, CloudEnvId, CloudEnvName and CloudTags. The Lansweeper API caps a single query at 30 fields, so the following columns are no longer imported: LsAgentVersion, LsPushVersion, LastActiveScan, LastIpScan, LastSccmScan, Department, DnsName, LastChanged and LastPatched. Review your attribute mappings if you currently rely on any of these.
  • Lansweeper sites the API token cannot reach no longer fail the whole import : Previously an import stopped as soon as it reached a Lansweeper site the API token was not authorised for. The adapter now skips those sites, imports the remaining ones, and reports a non-fatal warning naming the sites that were skipped so you can widen the token scope if needed.
Payment model
Free
License type
Atlassian Closed-Source

Learn and explore

  • What’s Marketplace
  • App installation
  • About Atlassian
  • Atlassian resources
  • Search and ranking
  • Atlassian events
  • Atlassian foundation

Follow