The wait is over…Assets Data Manager updates with the release of Schema Data Manager Import!

[#1]

We know what took us so long, right? Following numerous requests and an impressive number of upvotes for a feature we have seen in some time, we have enhanced the Assets Data Manager and launched the Schema Data Manager Import.

Atlassian acquired Airtrack and integrated it into Jira Service Management Assets, to help enterprises take a comprehensive approach to asset and configuration management. Over the past year, the team has diligently addressed open beta research, established baseline metrics, and masked your sensitive passwords and tokens when editing an adapter job, and migrated Airtrack to the Atlassian platform.

The value of Data Manager to customers centers on ensuring their asset data is complete, current, and correct, which empowers teams to make smarter operational and strategic decisions. Now, to add on it we’ve inlcuded Schema Data Manager import.

Schema Data Manager Import

The new Shema Data Manager Import is a built-in feature that enables seamless, direct import of Data Manager data into Schemas. When importing data into schemas, the new importer allows either creating new schemas (based on the Data Manager objects) or updating existing ones (using custom mappings).

How does Schema Data Manager Importer work

• You select a saved search in Data Manager as your data source.

• The importer can automatically create object types and attributes in a new schema, or you can map fields manually to an existing schema.

• Data is transferred efficiently, leveraging backend CSV functionality for reliability and performance

• Pro tip: Add Automation rule to schedule imports

Note: Full roll out to all customers will be finalized on August 31st.

New to Data Manager?

Join us for an upcoming community webinar on the Complete, current, and correct data: Intro to Jira Service Management Assets Data Manager on Sep 9, 12:00 – 1:00 PM (EDT)

Additionally, check out this step by step guide to get started or follow the beginning steps below:

How to configure Data Manager?

Configuring Data Manager involves four key steps, outlined below:

1. Integrate: Set up jobs to ingest data into Data Manager.

2. Cleanse and Reconcile: Establish attribute mapping, eliminate unnecessary data, define the normalization process, and consolidate the data into the appropriate objects.

3. Import to Asset Schemas: Transfer only the relevant data to the schemas.

4. Optimize: Create searches and dashboards to analyze the data effectively.

play.goconsensus.com

For an overview, watch this video that outlines the steps to configure Data Manager: Data Manager flow and how to configure [15 min].

Data Manager How-to videos

Below is a collection of brief videos designed to help you get started with configuring Data Manager:

Step	How to video	Related Documentation
Enable Data Manager	How to enable Data Manager in your instance and set permissions [3 min]	Enable Data Manager
1 - Integrate	How to create a job using a Flat File adapter [5 min] How to create a job using the Lansweeper adapter [5 min]	Create a job to ingest data Move data into Data Manager to create raw data Learn about Adapters
	How to run a job [5 min]	Run a job Download Data Manager clients
	How to transform the data [5 min] - optional step.	Transform data Transformation functions
	Automating data ingestion (refer to the documentation)	Automating data ingestion
2 - Cleanse and Reconcile	How to map the data [5 min]	Mapping data sources to an object Check the Data Manager out-of-the-box Object classes
	How to cleanse the data [4 min]	Configure cleansing rules Cleanse your data
	Normalizing data ( refer to the documentation)	Compute Dictionaries Configure Custom Computed Dictionaries
	How to reconcile the data [2 min]	Reconciling data from multiple sources (it is called “Import”)
	Automating cleansing and reconciliation (refer to the documentation)	Cleanse your data using the Cleanse and Import client for MacOS Cleanse your Data using the Cleanse and Import Client for Linux Cleanse your data using the Cleanse and Import client for Windows/DOS
3 - Import Data Manager data to schemas	Create searches (refer to the documentation)	Create searches
	Import data into schemas (Native Data Manager importer feature Please refer to the documentation for other options.	Import data into schemas using CSV data Import data into schemas (Scheme Data Manager Importer feature
4 - Optimize	Create searches (refer to the documentation)	Create searches
	Create dashboards (refer to the documentation)	Create dashboards

Data Manager in-product Setup Guide

An alternative way to learn how to set up Data Manager is by following the in-product setup guide.

To access the Data Manager in-product guide, simply click on the “Import and Analysis” menu option. From there, you can easily navigate through the various stages to set up Data Manager.

Important note:

Configuring Data Manager is a one-time process. You will only need to adjust the settings when introducing new data sources, modifying attributes, or creating new normalization tables, among other scenarios.

---

FAQ

What is Data Manager?

Assets Data Manager makes it easier to integrate, transform, and analyze data from multiple sources so you can ensure complete, current, and correct asset datasets.

Find out more about what Data Manager is and what it can be used for on our Assets Data Manager webpage.

How do I get access?

There’s no further action needed. Data Manager will be available to all Premium + Enterprise subscribers in Jira Service Management, cloud. It will be an opt-in feature of Assets that can be toggled on through the Assets' General Configuration Screen.

What should I prepare now to hit the ground running?

If you haven’t already, we encourage you to have a look at the blog: How to set up Assets Data Manager or check out the product documentation: Connect, cleanse and reconcile data with Assets Data Manager | Assets | Atlassian Support

[Jared Wallen]

is there an API for interacting with Assets Data Manager?

[Karyn Findlay]

@Jared Wallen ,

Unfortunately no API for Data Manager as yet.  It is in our backlog but not yet prioritised.

Regards,
Karyn

[Jared Wallen]

@Karyn Findlay that's disappointing and frustrating. i wish you (not you personally) would have waited to release this feature until this was complete. this is a great feature but without api access it's incomplete.

[Josh]

@Jared Wallen I understand the frustration, but there are a lot of customers that do not prioritize the API as much as simply being able to use the feature via the GUI. If Karyn and team waited to release this functionality until the API was ready, customers like me would be giving them a hard time for having to wait even longer.

Not many tears are shed in the Community for the challenges faced by Atlassian product teams, but in this case it seems like they made the most reasonable choice given the realities of the situation.

[Jared Wallen]

@Josh That's a fair argument. I would also say, though, that some of the problems for the product teams are self inflicted by releasing incomplete features, this just being one example. 

[Josh]

@Jared Wallen I'm nodding right now. :-)

It seems like Atlassian's general approach to rolling out features and products leans more heavily on the minimal part of MVP at times. I see that most often with products that lack role-based access controls and backup/restore capabilities. They're often saved for future development efforts, which can leave out companies that heavily rely on what many would consider "table stakes" functionalities.

My only semi-solution to impacting that thought process is to speak early and often with Product Managers to emphasize what is truly needed early on while resources are allocated to development. I've found providing feedback after something is launched to be much less effective; resources and attention start shifting elsewhere at that point. The concept doesn't help in this situation, but it may help you in the future...

[Jared Wallen]

@Josh yeah i completely agree. Their definition of M is definitely lower than mine. I'm relatively new to the admin side of this platform as i joined my team less than a year ago. I plan to be more involved feedback like this just as you suggest.

[Silvia Davis]

@Jared Wallen I also recommend voting for the API feature. It helps get it faster in the backlog prioritization ;-)