Best Practice for managing Desktops with their accessories called Keyboard, Monitor, Mouse
Asked by PK:

Hello Community!

We want to manage Desktops with their accessories called Keyboard, Monitor, Mouse, so wanted to know the best practices to implement in Jira asset management.

We were going to manage Keyboard, mouse and monitor over JSM, how to make relation between Parent and child, best practice will help us.


Answers:
author: Ashok Shembde
body: Hi [@PK](/t5/user/viewprofilepage/user-id/5559298) ,

To effectively manage desktops and their accessories (Keyboard, Monitor, Mouse) in Jira Asset Management (JSM), you can implement a **Parent-Child relationship** between these assets. Here are some best practices for setting it up:

### 1. **Define Object Types for Assets** {#toc-hId--2124520848}

* **Create separate Object Types** in Assets for Desktop, Keyboard, Monitor, and Mouse. Each type can represent a category with its own attributes (e.g., Serial Number, Model, Manufacturer).

### 2. **Set Parent-Child Relationships** {#toc-hId-362991985}

* Use **object attributes** in Jira Assets to link accessories to their parent desktops.
* For example, add a **Parent Attribute** to Keyboard, Monitor, and Mouse objects, which references the desktop they are linked to. You can do this by creating a custom field in these object types that references the **Desktop Object Type**.

### 3. **Use Asset Schemes and Object Schemas** {#toc-hId--1444462478}

* Organize your assets using **Object Schemas** for easy management.
* Under the schema, create **Object Types** like Desktop, Keyboard, Monitor, Mouse, and link them by using **reference attributes** (e.g., each keyboard, monitor, and mouse has a reference to a desktop).

### 4. **Tracking the Lifecycle of Assets** {#toc-hId-1043050355}

* Use **JSM automation** to automatically track and update the lifecycle of both the parent (desktop) and child assets (keyboard, mouse, etc.) when changes are made.
* For instance, if a desktop is decommissioned, the associated child objects can be automatically updated or flagged for review.

### 5. **Visualize Relationships** {#toc-hId--764404108}

* Utilize the **graph view** in Jira Assets to visualize how assets are connected. This will help you see how each desktop links to its accessories and provide a visual overview of the relationships.

### 6. **Use Issue Types for Asset Requests** {#toc-hId-1723108725}

* Create a **Request Type** specifically for accessories or desktop-related issues.
* If a desktop needs to be serviced, use the asset field to bring all associated assets (keyboard, monitor, etc.) into the ticket.

By following these practices, you'll have an efficient, scalable system for managing desktops and their related accessories, keeping track of asset relationships and statuses within Jira Asset Management.


author: Emily _ DevSamurai
body: Hi [@PK](/t5/user/viewprofilepage/user-id/5559298)

There are some approaches I can suggest, based on your use case, as follows:

1. With the [**Assets**](https://www.atlassian.com/software/jira/service-management/product-guide/getting-started/asset-and-configuration-management#how-it-works) feature in Jira Service Management:

* You can first define your **Asset Object Types** and **Schemas** by creating a separate schema (like "IT Assets" or "Hardware") in your JSM Assets. Then, define object types within the schema:
  * **Desktop** (Parent)
  * **Keyboard** (Child)
  * **Monitor** (Child)
  * **Mouse** (Child)
* For each object type, set up necessary attributes that capture important information. For example:
  * **Desktop:** Asset Tag, Model, Serial Number, Location, User, etc.
  * **Keyboard, Monitor, Mouse:** Serial Number, Model, Associated Desktop, etc.
* Use attribute types such as Text, Number, Status, and Object for relating other object types.
* Use the **Object** attribute type to establish relationships between the Desktop (Parent) and its accessories (Children).
* In the **Keyboard, Monitor, and Mouse** object types, add an attribute like "Associated Desktop" with a type "Object" referencing the Desktop object type. This creates a link from the child to the parent.
* Here is the Best Practice and Tips for **Assets** : [Asset and configuration management best practices and tips](https://www.atlassian.com/software/jira/service-management/product-guide/getting-started/asset-and-configuration-management#best-practices-and-tips).

2. With the [**AssetIT**](https://marketplace.atlassian.com/apps/1228867/?utm_source=atlassian.community&utm_medium=answer&utm_campaign=recommendation) app:

AssetIT is an IT asset management plugin for Jira, which can also solve your use case with:

* Add*Desktops* to the Assets group.
* Add*Keyboard, Monitor, and Mouse* to the Accessories group.
* Assign *Keyboard, Monitor, Mouse*to the Desktops. (In AssetIT, Assets play as a central role, which can be connected with other assets, accessories, licenses, consumables, components, etc.).
* Integrate Assets/Accessories to Jira projects to manage from there.
* Related document: [AssetIT Case Study for IT Industry](https://assetit.app/it-service-company/?utm_source=atlassian.community&utm_medium=answer&utm_campaign=recommendation).

I hope this will help. Let me know if you have any questions :).


author: Ahmad Mughal
body: To manage desktops and accessories in Jira Asset Management (JSM):

1. **Use Parent-Child Relationships**:

   * Set **Desktop** as the parent asset.
   * Link **Keyboard, Monitor, Mouse** [as](https://instavipbio.net/) child assets using the **"References"** or **"Relates to"** field.
2. **Create Asset Schemas**:

   * Define asset types for Desktop, Keyboard, Monitor, and Mouse for better tracking and relationships.


Tags: cloud

jira-service-management

jira-service-management-cloud