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

How do I create attributes in Asset Objects that source fields in Jira Service Manager?

Alex Brockbank

We're just starting to use Assets. How do I create Attributes (fields) in Assets that source existing data in fields that are already in use in Jira Service Manager? (such as Department, Location, etc).

I do not want to duplicate lists between Jira SM and Assets schemas.

Accepted answers

Yogesh Mude_f9cg0f

@Alex Brockbank Welcoem to the community!

You can create a Department attribute in the schema object and add the options in it. Then create a department assets field in the Jira and in the field conext, configure the schema to use the object schema department attribute.

WIth this you dont need to add the department field option in the jira assets field, but it will fetch the values from the object schema department attribute and show.

All comments

Yogesh Mude_f9cg0f

@Alex Brockbank Welcoem to the community!

WIth this you dont need to add the department field option in the jira assets field, but it will fetch the values from the object schema department attribute and show.

Alex Brockbank

Thank you, Yogesh. Does this mean that the Jira Service Manager is looking up "Department" from the Assets database, not the other way round?

Currently I have a "department" field in Jira SM, already populated. I was hoping that when a user name was added to an Asset, it would automatically populate the "Department" field in the Asset by extracting the data from the Jira Service Manager.

Yogesh Mude_f9cg0f

Nope, i dont think its possible.

To know the department based on the username, the both username and department should be there in the assets schema. and you can use these attributes to show the data on the jira work items with the help of assets fields.

Yogesh Mude_f9cg0f

Also, the advantage of the assets object and attributes is that you can add more n more attributes like address, managers, skills etc+ filters so that you dont need to create seperate jira custom fields for each attibute.

If you have a single assts field called (lets assume, employee etc) then you can just use the assets object to show all the details of that employee like his, department, manager, skills, address etc.

Samuel Weiss_3fzznz

Hi @Alex Brockbank

if I understand correctly you need to have a copy of JSM customers in Jira Asset. If so ... we have just released a small sync app grabbing all organisations and customers from Jira Service Management and sync them into Jira Asset including ALL custom attributes.

Customer as an Asset

In case of question, please reach out.

Samuel

Alex Brockbank

Many thanks, Samuel.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management