JSM Premium and the newest Assets Practices?

[QMSpot _ Patrick Gehlich]

Hello Community :)
I just start to learn the Assets Functions in our Service Collection Premium.

I see a lot different tutorials, because there were some major changes recently.

I want to set up some Demo Assets:
Customers Organization (Domain) - Customer Contact: Name, Email Adress - Customer Device (Laptop).
Everything as Assets Scheme.

Now Rovo told me, i can connect this scheme to my JSM Project:

Sure! Here's the previous explanation in English:

---

How Assets Customer Mapping Works

1. Email-Based Customer Matching

• Create an Email attribute on the Object Type "Contact" (or "Ansprechpartner")

• In your JSM project go to Project Settings → Assets → Customer Mapping and configure:

  • Object Type: Contact

  • Match field: Email

  • Match against: Reporter email of the ticket

• Result: When max.mueller@customer.de creates a ticket, JSM automatically finds the contact "Max Müller" and links the full chain — Organisation, Location, Hardware etc.

2. Domain-Based Organisation Matching (Fallback)

• Add a Domain attribute to the Object Type "Organisation" (e.g. customer.de)

• If someone new with @Customer.de submits a ticket and doesn't exist as a contact yet, JSM can still match them to the correct organisation based on the email domain
  
  
  

I absolutly don´t find the Assets Settings in my JSM Project.
I activated all functions, premium Functions.

Can someone lead me to the newest Tutorial or help page?

i want to manage a little Basic, that we can match the Customers Domain, Email adress etc. coming from the assets to the Service Project issues. 

And it´s very important that we can "link" one Scheme to one JSM Space.
We need to provide IT Service for a Enterprise customer, which Assets needs to be seprated from the others :)

Thanks a lot :)
Patrick

[Mikael Sandberg]

The way you link a JSM project to your assets is that you create a new custom field using the Assets object field, then you configure that field to display objects in Assets. This getting started tutorial shows how to do this.

[QMSpot _ Patrick Gehlich]

I read through.
That´s far from easy administrating Assets in JSM like advertised from Jira.
Sorry to tell this.

Does someone know a Marketplace App, which does all this Custom fields and Automations for us? We are a very small team and dont have time to jump into this world.

We really just need some Basics like:
Organization, Employee, Laptop etc.
This needs to be shown in the Issue later. 

Also, when the Reporter is not an asset yet, a automation needs to create the reporter as asset in the correct Scheme for the matched Organization.

My brain is really exploding, sorry :D

And Thank you and good night :)

[noorfatiima502]

Hi Patrick,

You’re definitely not alone — the recent changes around Assets in Jira Service Management have made things a bit confusing, especially compared to older tutorials.

A couple of important clarifications that might help:

1. The “Customer Mapping” settings you’re referring to are not always visible in all environments yet. In many cases, the connection between Assets and a JSM project is still primarily handled via Assets Object custom fields inside the project.

2. To “link” Assets to your JSM project, the current recommended way is:

   • Create an Assets Object field

   • Configure it to point to your specific Object Schema

   • Add it to your request types / issue view

3. For your use case (Organization → Contact → Device), your structure is absolutely correct. However, the automation part (auto-create contact when reporter not موجود) still requires:

   • Jira Automation rules

   • OR custom scripting / marketplace apps

4. Regarding Marketplace apps:
   There isn’t (yet) a fully “one-click” solution that handles schema + mapping + automation out of the box. Most teams still combine:

   • Assets + Automation

   • Sometimes apps like ScriptRunner for Jira for advanced logic

👉 Honest advice:
Start very simple first (just 1 schema + 1 object field in issues), then gradually add automation. Trying to implement full domain/email mapping from day one can get overwhelming quickly.

Also, for separating customers:
You can absolutely use separate Object Schemas per customer, and restrict visibility via roles/permissions — that’s the standard approach.

Hope this helps a bit and reduces the “exploding brain” feeling 😄
You’re on the right track — it just takes a bit of setup initially.

[QMSpot _ Patrick Gehlich]

hello @noorfatiima502 
wooooah THANK YOU so much for this very detailled Feedback. :)
This Community and all the Atlassian and Marketplace Apps Support is the best i´ve ever experienced :)

You wrote:

1. The “Customer Mapping” settings you’re referring to are not always visible in all environments yet. In many cases, the connection between Assets and a JSM project is still primarily handled via Assets Object custom fields inside the project.
   
   
   
   So this means, that a Update is rolling out, to make it easier to map a Scheme to a JSM?

Thank you very much. I will try it. 
Have a nice evening and weekend :)