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

User to CI reference

Denis_gxx8zu

Hello, community!

I've recently started testing Assets.

First step: I have successfully imported the organisational structure and employees.

Second step: I've manually added a list of test CIs.

Next step: I need to make a link between User and CI. One user can have links to multiple CI and vice versa - one CI can have links to several Users. And here I've failed - have no idea how to link User to CI.

I'm asking the community for help

Accepted answers

Stefan Stadler

Hi @Denis

this one is quite simple. You need to add the relation on one of the object types. The objects will then actively get assigned the other objects. From my understanding, it would make sense to define this attribute on the User object type. Open the Object type, click on Attributes and create a new attribute. You need to choose it similar to the following screenshots (I used "Procedures" instead of "CI", so replace as needed):

Once you are done, click on the cog icon > Configure. In the tab Cardinality, select Unlimited as I it sounds like there can be a larger number of CIs assigned.

Whenever you now specify the relation on the user object, you will directly see the related CI (see here using the example from above):

This is called an outbound reference. The opposite (inbound reference) is automatically created on the referenced object (in this case Procedure "GP4-3"):

You can then expand this to see the details. If other objects refer this Procedure object, there would be more than one listed here.

You can read more about this here, which gives a full example as well:

Tutorial: Starting from scratch | Jira Service Management Data Center 10.1 | Atlassian Documentation

I hope this helps

Regards,

Stefan

All comments

Stefan Stadler

Hi @Denis

Once you are done, click on the cog icon > Configure. In the tab Cardinality, select Unlimited as I it sounds like there can be a larger number of CIs assigned.

Whenever you now specify the relation on the user object, you will directly see the related CI (see here using the example from above):

This is called an outbound reference. The opposite (inbound reference) is automatically created on the referenced object (in this case Procedure "GP4-3"):

You can then expand this to see the details. If other objects refer this Procedure object, there would be more than one listed here.

You can read more about this here, which gives a full example as well:

Tutorial: Starting from scratch | Jira Service Management Data Center 10.1 | Atlassian Documentation

I hope this helps

Regards,

Stefan

Denis_gxx8zu

@Stefan Stadlerthank you for the concise and accurate explanation! I've managed to create CI user links.

May I ask one more question: I would like to see the reference type, e.g. User1 has access to VM1 via ssh. What is the best approach in this case?

Stefan Stadler

Hi @Denis ,

not sure, if this would be best practise, but I could imagine the following 2 options to be working fine:

a) Create an attribute on the User object type similar to CI, but name it SSH access (or access in general) and configure it to refer to the CIs. That way, you could separately set those connections.

b) Create a new object type "Access" or "Credentials", where CI and User are configured as references. Additionally, I would add an attribute "Type" as a select list, where you can select, if this connection is SSH or RDP or whatever you want to add there. You can then specify the User and the CI object as well as the type. This will then be reflected as inbound references on the User and CI objects as well.

However, this would cause quite a lot administrative overhead, so check if it might be already enough to have "User" linked to "CI".

Regards,

Stefan

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-data-center

data-center

assets