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; } } }

We need YOU to help define Assets' Common Data Model

Dorothea Linneweber

Hello community!

We're on a mission to evolve the schema templates in Assets in Jira Service Management to help you move in quickly, and gain value fast! To do that, we need your expertise…

Are you an Asset Manager, System Administrator, Configuration Manager, or similar for a large company? Do you use Jira Service Management, other service management tools, or dedicated ITAM software? Join our research study to directly shape the development of Assets' Common Data Model, a set of (optional) schema templates to support key service management practices. You’ll get to:

Preview proposed schema structures and provide feedback. Share your thoughts on the suitability and usability of our proposed data models for your organisation.
Discuss your real-world Assets applications, use cases, and requirements. Your practical experience will help us ensure that the data in Assets' Common Data Model can support a broad range of use cases.
Contribute to a more effective and integrated Assets experience across the System of Work. Help us build the solution that streamlines your daily tasks and empowers you to make better decisions.

This research involves a brief commitment of 1 hour for an interview, followed by an optional lightweight diary study. Your insights will be invaluable in ensuring that Assets' Common Data Model meets the practical demands of real-world asset management.

If you're interested in contributing to this important initiative, please sign up by filling out this form. Limited spots are available, so register soon! We appreciate your time and valuable expertise.

Looking forward to chatting soon!

Doro

Senior Product Manager, Jira Service Management

Comments

Antonio Valle _G2_

@Dorothea Linneweber this initiative is really interesting. Atlassian will provide much more value than giving an empty database that has to be designed and filled by every customer. Even when every customer or every service project is different.

I would add that this value can be provided not only by Atlassian using predefined templates, but also can be provided by partners (providing partner-crafted templates, this can be a differential value aded) and even better, by customer (to internal departments or customers liberating knowledge and experience to the community).

So to be the change you seek and to unleash the power on every team, a functionality to share templates would be of great value!

Josh

@Dorothea Linneweber please count me in.

It was great seeing your presentation with Lucid Motors at TEAM this year.

Nadine Alexandra Schütt

Hello @Dorothea Linneweber

I came across this post looking for any import feature for the already existing Services scheme in Assets to realize Atlassian is about to add more common schemes like that. The roadmap teases Q2/2026 as the target release for CDM so I am wondering whether this is still the plan and if you can already share details on which common schemes will be introduced. We are working on Assets right now so details on what will change would be helpful to avoid conflicts with our plans ;-)

Also still very much interested in an import feature since that limitation already proved challenging with the existing services scheme.

Shari Barchus

@Dorothea Linneweber Would you be able to provide an update on the upcoming release? We are also currently kicking off a large Assets implementation. It would be so help to avoid any re-work that might be needed once this rolls out. Thank you

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-cloud

itsm

asset-management

jira-service-management-cloud

jira-service-management

assets

esm