Jira is not only a tool for managing projects, tasks, tickets and bugs but also a powerful way to manage and track assets, making it an even more indispensable tool for teams.
But what exactly is an asset?
An asset can be defined simply as the physical or digital representation of a resource.
Here are some examples of assets that can be tracked:
Hardware: computers (desktops, laptops, tablets), servers, network devices (routers, switches, firewalls), peripherals (printers, scanners, projectors), phones and mobile devices.
Contracts: IT services (email, backup, antivirus), support contracts, subscriptions.
Facilities: buildings, offices, warehouses, machinery, vehicles, furniture and fittings.
Access: badges, keys, permits.
Why are Assets important in Jira?
“Why are assets so important?” is a question we often ask ourselves when we hear about assets. Let us look together at the main characteristics of assets.
1. Total Visibility and Transparence
They provide a complete and updated view of the organisation. In particular:
Allows you to know what you own, where it is and the state it is in.
Avoids duplicate purchases.
Facilitates the identification of what we need, saving time.
2. Optimized Lifecycle Management
Every asset goes through a lifecycle, from procurement and deployment to retirement. Managing this lifecycle is crucial to ensure that resources are not only available but also functioning at peak efficiency. With Jira, teams can:
Track the entire life cycle of each asset, from its purchase to its disposal.
Effectively plan maintenance and replacements.
Reduce costs through more efficient management of resources
3. Automation for Efficiency
Jira allows the automation of resource management. For example:
Assets can be automatically assigned to issues or team members.
Alerts can be set up to alert users when an asset nears the end of its life cycle, needs maintenance or requires an upgrade.
It is possible to automatically generate reports on the status, utilisation and performance of assets.
4. Compliance
Asset management is crucial to comply with IT security and asset management regulations and to keep track of sensitive data associated with them.
5. Decision Making
Asset data can be used to make strategic decisions, such as the purchase of new assets or the replacement of obsolete ones.
Example of use: Management of onboarding and offboarding
With the asset management tools it is possible to create an onboarding profile that includes all the resources to be assigned to the new employee. This profile can be configured to include all details such as the type of device needed, software licences, and even access to certain office areas or digital resources.
We can then automatically assign assets when a new employee is registered, monitor the availability of resources and track their status.
Similarly, offboarding can be managed effectively and automatically: checklists can be generated listing all assets that need to be returned, access and licences can be revoked, and a ticket can be automatically opened to verify the integrity of the returned assets or to return them.
In Conclusion
Assets in Jira are a powerful tool for any organisation that wants to have complete control over its assets. In fact, by integrating asset management into Jira, organisations can gain a deeper level of control, visibility and efficiency in the management of these essential assets.
Thanks to their ability to connect information in an intuitive way, assets can transform Jira into a true command centre for managing corporate assets, ensuring success and maximising productivity.
A practical look at SAFe, LeSS, Scrum@Scale, Disciplined Agile, Nexus, and custom hybrid models for enterprise IT organizations using Jira, Jira Service Management, and Confluence Cloud. Scaling Agile in the Enterprise: The Question Nobody Really Wants to Answer For many Read More
Today, there are many solutions available for IT asset inventory management, such as GLPI. However, these tools often lead to fragmented data spread across different databases that don't communicate with each other, except through custom-built interfaces. The Challenge The goal Read More
TL;DR: In GLPI, access permissions for assets have traditionally been tied mainly to entities. That works well in clean structures, but in reality, responsibility, ownership, and organizational hierarchy do not always follow the same lines. With GLPI 11, group-based permissions Read More
The current architecture and underlying technologies behind the Atlassian Rovo engine, in light of recent developments The last few months show the path forward If you've been following the evolution of AI in recent years, you know changes come fast Read More
When setting up Jira Service Management (JSM), one of the most fundamental questions administrators face is, “Should we consolidate everything into one giant project, or split our teams into separate projects?”, this choice impacts agent productivity, reporting clarity, portal experience, Read More