Atlas Bench blog

Guide: The Lifecycle of an Asset Inside of JSM

Written by Riley Venable | Jan 5, 2026, 4:38:13 PM

Managing IT assets throughout their lifespan is a complex but crucial undertaking. Ensuring assets are accurately tracked, proactively maintained, and efficiently retired is fundamental for achieving operational excellence within any organization. This blog post, derived from a recent presentation, delves into how Jira Service Management (JSM) can revolutionize asset lifecycle management. Through robust integrations and intelligent automations, JSM provides a seamless and highly efficient system for keeping precise track of every asset’s journey from acquisition to retirement.

Key Pre-made Configurations for JSM Asset Management

To effectively manage the asset lifecycle within Jira Service Management, certain foundational elements are configured. These pre-made configurations streamline the process and ensure all necessary data points are captured and utilized.

  • Asset Definition: For our demonstration, we utilized a common IT asset: a MacBook Pro. This asset type in JSM is configured with various essential attributes such as Cost, Type, Color, Status, and User, among others, allowing for comprehensive data capture relevant to its lifecycle.

  • Lifecycle Workflow: We designed a workflow specifically to mirror the real-world lifecycle stages an asset undergoes. This workflow dictates the transitions and states that our work items will follow, ensuring a structured progression from acquisition to retirement.

  • Custom Asset Field: To directly associate an asset with a work item or issue, a custom field of the 'Asset' type was created. This custom field is linked to the appropriate asset schema and screen scheme, enabling users to easily select and reference the relevant asset when submitting a service request or incident.

Scenario 1: Editing an Asset’s Status and User

One of the most common and vital aspects of asset management is updating an asset's status and its current user. Consider a scenario where a new laptop is being provisioned for an employee. By simply transitioning a work item to an "Assigned" status, the associated asset automatically updates its status to "Assigned," and the user attribute of the asset is updated to reflect the new owner, typically the reporter of the work item. This automation eliminates manual updates, reduces errors, and ensures that the asset's record accurately reflects its real-time status and assignment.

Scenario 2: Depreciation/Aging based on Time/Status

Automating the tracking of an asset's age or depreciation is fundamental for financial planning and inventory management.

  • Automated Age Tracking: A rule can be configured to automatically update an asset's "Age (Months)" attribute. For instance, this rule can trigger on the first day of each month at 9:00 AM, incrementing the "Age (Months)" field for all relevant assets.

  • Triggering Actions: Keeping track of an asset's age enables proactive management. When an asset reaches a predefined age threshold, an alarm or a specific action can be triggered. This could involve creating a new review task, initiating a replacement request, or flagging the device for end-of-life procedures.


Scenario 3: Incident Linking & Status Update

During an incident, it is critical to know which assets are affected and their current state. Imagine an incident is raised regarding a faulty laptop. When this "Affected hardware" asset is linked to the incident, and the work item is transitioned to "Under Maintenance," the asset's attribute automatically changes to "Under Maintenance" or "In Incident." Furthermore, an automated email can be dispatched to the reporter of the issue, informing them of the status change and, if necessary, requesting details for a replacement device while the original is undergoing repair. This ensures transparency and efficient communication during critical service disruptions.


Why JSM for Asset Lifecycle Management?

Leveraging Jira Service Management for asset lifecycle management offers significant advantages that streamline operations and enhance decision-making.

  • Centralized Data: JSM and Assets collectively provide a single, integrated platform. This eliminates disparate data silos, improving overall data consistency and ensuring that both service requests and comprehensive asset information are managed from one source.

  • Enhanced Visibility: The platform offers real-time insights into asset statuses and their interrelationships. This enhanced visibility across your asset landscape facilitates informed decision-making, from procurement to retirement.

  • Operational Efficiency: Automation capabilities within JSM dramatically reduce manual effort, minimize the potential for human error, and accelerate workflows associated with asset provisioning, ongoing maintenance, and eventual retirement.

  • Flexibility and Customization: Jira Assets allows organizations to define highly specific schemas for virtually any type of asset. This flexibility ensures that the solution can be precisely tailored to your unique organizational needs and diverse asset types, extending beyond just IT hardware.