Use Case Examples for Assets
Welcome to the Pio Software Use Case Library.
Here you will find practical examples of how our apps can be applied to real scenarios in Atlassian’s Jira Service Management and Jira Assets.
Each use case is grouped into two formats:
Articles — in-depth guides with context, configuration patterns, and best practices.
Quick Scenarios — for fast insights.
Every use case is tagged with the relevant Pio app(s), so you can immediately see which product applies.
📌 Tip: Most support questions we receive are already answered here – check the use cases first to save time!
1.) Articles
Articles include both detailed guides and reference-style resources that go beyond quick scenarios.
Here you’ll find:
In-depth guides explaining how to set up and use specific features.
Real-life use cases that demonstrate practical scenarios.
Reference resources such as dictionaries, example queries, or configuration tips.
These resources are designed to give you more context and hands-on examples than the Quick Scenarios, helping you understand not only what is possible but also how to achieve it effectively.
Use Case Name | Description | Related Pio App(s) | Link | |
|---|---|---|---|---|
| 1 | Finding managers of users and setting them as approvers automatically | Automatically assigns a user’s Manager (from Entra ID) as the approver in Jira Service Management requests. | Microsoft Entra ID Importer for JSM Assets | |
| 2 | Mapping Azure AD (Entra ID) Users with Jira Users and Jira Groups | Aligns Entra ID user accounts and groups with Jira identities for consistent access and permissions. | ||
| 3 | Filtering Records for Cost Saving and Higher Efficiency | Uses filters to limit imported records, reducing unnecessary syncs and optimizing system performance. | All Importers | |
| 4 | Keeping track of the deleted records | Tracks deleted items during synchronization to maintain data integrity in Jira Assets. | All Importers | |
| 5 | Keeping track of the empty values | Ensures empty/null values in source systems are consistently handled in Jira Assets. | All Importers | |
| 6 | Managing Multiple Object Schemas in JSM Assets | Enables structured management of multiple object schemas in Jira Assets. | ||
| 7 | Connecting Multiple Object Schemas and having an aggregated data model. Such as:
| Links different object schemas for cross-schema relationships (e.g., users ↔ devices). | Microsoft Entra ID Importer for JSM Assets | |
| 8 | Understanding JSM Assets Security | Explains access rights, roles, and security configuration in Jira Assets. | General (Assets) | |
| 9 | Getting additional details of the requestor's manager | Enriches request context by importing manager attributes (e.g., department, location). | ||
| 10 | Keeping track of Infrastructure Resources | Track infrastructure resources in Jira Assets with AQL to quickly filter environments, products, and related components. | ||
| 11 | Allowing JSM customers to select their devices while they are requesting help | Lets end-users pick their registered devices in the JSM portal when raising a request. | ||
| 12 | Adding Device Types for Microsoft Intune Managed Devices | Imports Intune device types into Jira Assets for classification. | ||
| 13 | Handling long text values | Explains how to manage and map attributes containing long text strings in Jira Assets. | All Importers | |
| 14 | 2 different ways to manage the external Identifier | Shows approaches for managing external IDs for records across systems to keep data consistent and traceable between source systems and Jira Assets | All Importers | |
| 15 | How to use Assets and JSM for reporting broken hardware | Demonstrates a real-life scenario of tracking broken devices in Assets and creating JSM requests based on accurate device data. | Microsoft Intune Importer for JSM Assets | |
| 16 | How to customize the Object Schema | Explains how to modify object schemas to fit organizational needs. | General (Assets) | |
| 17 | Using Existing Object Types | Leverages built-in object types to save time when designing schemas. | General (Assets) | |
| 18 | Assets Dictionary for Beginners | A beginner-friendly glossary of Jira Assets terminology and concepts. | General (Assets) |
2.) Quick Scenarios
Short descriptions that highlight what is possible with Pio Software apps. Ideal for a quick overview or inspiration.
Use Case Name | Key Benefit | Related Pio App(s) | |
|---|---|---|---|
| 1 | Taking decisions based on the office locations of the employees | Automate request routing and approvals based on office location | |
| 2 | Setting the owner of a device | Link end user devices to their owners in Assets | |
| 3 | Searching for the owner of a device | Search and identify who owns a device across systems in seconds. | |
| 4 | Notifying responsible teams before expiration dates | Proactively alert teams about approaching expiration dates such as:
| |
| 5 | Monitors consumed and enabled license units and notifies you before over- or under-utilization, helping you stay audit-ready. | Stay audit-ready and optimize license consumption | |
| 6 | Keeping the inventory of managed end user devices | Maintain up-to-date inventory of laptops, desktops,tablets, phones etc. | |
| 7 | Finding the people in the same AD Group and sending them a notification | Notify all members of a specific AD group at once | |
| 8 | Using automated Service Dependency Mapping for Hosts for impact analysis | Identify host dependencies automatically to support impact analysis. | |
| 9 | Reviewing the important information about devices and taking automated actions | Review device states, compliance, OS versions, serial numbers; take automated actions | |
| 10 | Keeping track of the whole IT Infrastructure (AWS, Azure, GCP, Alibaba Cloud, Oracle, SAP, etc.) | Centralize visibility of infra assets across platforms |
More details to come…