Hello Community! 👋 If you haven't heard about our Jira Guru, it's a series of step-by-step guides on Jira by DevSamurai. I am excited to introduce one of our latest guides, which is about working with Assets in Jira Service Management. Let's dive into it right away!
This discussion is designed to make asset management in Jira Service Management approachable and straightforward, breaking down the jargon into easy-to-understand concepts. We'll show you why managing assets is crucial for any organization and how it can make your life easier, save you money, and ensure you're always prepared. Let's dive into the world of assets together and see how they can transform your service management experience.
In Jira Service Management (JSM) Cloud, "Assets" stands out as a key feature designed exclusively for Premium and Enterprise tiers, focusing on the intricate world of asset and configuration management. This specialized tool caters to company-managed projects, offering a robust solution for tracking a wide array of assets and configuration items (CIs), from hardware and software to services and beyond.
If you're using Jira Service Management's Premium or Enterprise versions, you're in luck—Assets is readily available in the top navigation bar of your JSM projects. For those on the Free or Standard plans eager to leverage Assets, an upgrade is necessary through Settings > Billing > Manage Subscriptions.
Managing assets in Jira Service Management is a game-changer for any team looking to streamline their IT and service management processes. Here’s why it’s a must-do:
By linking customer assets, or objects, directly to service requests, IT teams can solve problems more quickly. This direct link provides immediate access to all necessary asset information, speeding up the resolution time and improving customer satisfaction.
Understanding the downstream impact of changes on assets helps teams anticipate and mitigate risks before they become issues. This foresight is invaluable for maintaining system stability and preventing unforeseen disruptions.
With detailed visibility into the infrastructure, teams can locate and address underlying problems more effectively. This deep insight helps in identifying patterns or recurring issues, leading to more sustainable solutions.
Tracking assets is essential not just for day-to-day operations but also for strategic planning, audits, and compliance activities. Knowing what assets you have, their status and their history helps in making informed decisions, ensuring legal compliance, and preparing for audits with confidence.
Assets in Jira Service Management is designed to work seamlessly with ITSM practices. It allows teams to tie assets and configurations directly to service requests, incidents, problems, changes, and workloads. This integration ensures that asset management is a part of the workflow, not an isolated task.
The flexible and open data structure of Jira Service Management’s asset tool stands in contrast to traditional configuration management databases (CMDBs). It supports the management of any kind of asset, making it a versatile tool not only for IT teams but also for HR, sales, marketing, legal, and facilities management. This versatility means that virtually any department can leverage Assets to track and manage their resources effectively.
Setting up Assets in Jira Service Management is a foundational task that enhances your service and asset management strategy. Here's a structured approach to get started, ensuring your team can manage and track assets efficiently within your organization.
What is a Schema? Think of a schema as a big folder that contains all your asset types (like servers, laptops, software) and individual assets. It's the organizational structure for everything you'll track.
Sample IT assets schema
Here's the view of an object schema, based on the sample IT assets schema, pre-filled with data. (Source: Atlassian Document)
If you're migrating from another system or have a pre-existing database of assets, use the Import feature to bulk-create object types and objects. This saves time and ensures consistency across your asset database.
Learn more about Get Started with Assets in Jira Service Management with Atlassian document here
When creating or updating a service request, incident, or any other issue type, you can link relevant assets directly to the issue. This linkage provides context and vital information for resolving the issue more effectively.
To build a comprehensive view of how assets relate to each other (e.g., which server a specific application runs on), you can create and manage relationships between assets.
To effectively use the Assets Dashboard in Jira Service Management, follow these steps:
Troubleshooting common issues in Jira Service Management's Assets feature is essential to ensure smooth operation and effective asset management. Here's a step-by-step guide to help you address and resolve these issues:
Take your asset management in Jira to the next level with AssetIT by DevSamurai Team. It offers advanced features like customizable workflows, powerful reporting, seamless integrations, enhanced security, and scalability. Upgrade your asset management experience today with AssetIT.
AssetIT also integrates seamlessly with Jira, especially with Jira Service Management, when it comes to sorting assets based on request types. With the Inventory feature, AssetIT stands out from other asset management software by correspondingly linking IT assets with the desired issue types, making the request resolution process more flexible and effective.
In closing, embracing Assets within Jira Service Management is a pivotal move towards optimizing service delivery and asset management. This guide has equipped you with the essentials, from understanding assets' significance to integrating them seamlessly into workflows. With Assets, you gain insights, streamline processes, and make informed decisions, ultimately enhancing service management practices. Continuously refine your approach, seek feedback, and explore advanced features to unlock greater value. By leveraging Assets effectively, you propel your organization towards delivering exceptional service and achieving success.
Hi @Piotr Witka , my apologies for the late response.
I would say both of the apps are beneficial in many ways, depending on your needs. If you're looking for a user-friendly and affordable solution of asset management, AssetIT would be top of mind. Meanwhile, if you're an expert in Jira Service Management, familiar with terms, definitions, and aware of its CMDB workflow, Assets would be a great choice.
To have a deeper insight into it, I suggest you to check out this article: Jira Insight Asset Management and AssetIT: Which one is for you?
I hope this will help!