New Admin Journey for Data Manager: Rolling Out to All Instances

[#1]

The new Admin Journey for Assets Data Manager will start rollout today . Assets Data Manager is part of the Assets within Service Collection - Premium and Enterprise plans. Over the coming weeks, all instances will transition to the new experience we introduced in our previous Community blog.

If you want a deeper dive into the new terminology, navigation changes, and updated workflows, please review the original Community blog. 

Quick recap of what changed

Here is a brief recap of the most important updates from our first blog:

• Updated terminology across Assets Data Manager to better reflect data pipelines, schedules, and source connections.

• A refreshed admin navigation that groups configuration, monitoring, and troubleshooting actions more logically for admins.

• Clearer status and health indicators for imports and synchronisations, making it easier to understand what is happening with your data.

• More consistent wording and labels across the experience so that admins and teams use the same language when talking about Assets Data Manager.

• An easier flow, making it more obvious what the next step is.

What is changing now

With this rollout, we are moving the new Admin Journey to making it the standard experience for all Assets Data Manager admins.

• All existing sites will be progressively switched to the new Admin Journey without requiring any manual migration.

• The legacy admin screens for Data Manager will be retired as your site transitions to the new experience.

• Configuration, schedules, and data connections that you have already set up will continue to work; what changes is how you access and manage them.

Rollout timing

The rollout to all instances will happen over the coming weeks. During this period, you may notice that your admin interface for Assets Data Manager changes to the new layout and terminology described in the earlier blog.

All of your Assets Data Manager documentation will be refreshed after 15 June 2026.

You do not need to schedule downtime or take any manual action for the changeover; it will be applied automatically to your site.

Who is impacted

This change primarily affects:

• Admins who configure and maintain Assets Data Manager imports, synchronisations, and data connections.

• Teams responsible for data governance, CMDB accuracy, and asset visibility who rely on Data Manager to keep information up to date.

• Support or operations admins who troubleshoot failed runs or investigate data quality issues in Assets.

End users who only view or use asset data in Jira or other Atlassian apps will not see major changes.

What admins should do now

To make the transition as smooth as possible, we recommend that admins:

• Review the original Community blog for the full list of terminology changes and UI updates.

• Share the terminology changes with your internal support and operations teams so everyone uses the same language when talking about Data Manager.

• Update any internal documentation, runbooks, or onboarding materials that reference old screen names or labels in Data Manager.

• If required, plan a short walkthrough for other admins in your organisation to show them where familiar settings and views now live in the new Admin Journey.

FAQ

Will my existing Data Manager configurations be changed?

Your existing configurations, schedules, and data mappings will remain in place. The rollout focuses on the admin experience and terminology, not on altering how your data flows are configured behind the scenes.

Do I need to opt in or enable the new Admin Journey?

No action is required to enable it. The new Admin Journey will be turned on for your instance automatically as part of the rollout over the coming weeks. If Assets Data Manager is not currently enabled in your instance, an Assets App admin can enable Assets Data Manager for you.

Will there be any downtime or risk to running imports?

The change is designed to be seamless. You should not expect downtime for Data Manager. Imports and synchronisations will continue to run as normal while the admin interface is updated.

Where can I find the detailed list of terminology changes?

The full rundown of terminology changes and key adjustments is documented in our original Community blog.

How can I share feedback or ask questions about the new experience?

Please use the comments on the Community blog to share feedback, ask questions, or highlight anything that is unclear in the new Admin Journey. You can also raise this with your internal Atlassian contact or through your existing support channels if you need help with a specific configuration.