We’re exploring the most efficient way to manage consumables—items like mice, keyboards, dongles, and cables—in Jira Assets. Our key requirements are:
No individual object for every single item
Creating hundreds of tiny objects clutters the schema and slows everything down.
Simple issuance & return workflow
Service-desk agents should be able to hand out (or return) a consumable in just a click or two.
Per-user consumption history
We still need to report how many of each consumable an employee has received over time (for audit and budget forecasting).
Questions for those who’ve solved this
Object design: Did you use a single “Consumable” object type with attributes like Category (mouse, keyboard, etc.) and Quantity on Hand? Or something else?
Transactions: How do you record each issue/return event—custom “Inventory Transaction” objects, automation rules, or JSM forms?
Automation: Any Asset automations or Jira Automation rules you’d recommend to keep quantities in sync?
Reporting: What’s your go-to method for pulling “Who has received how many of X?”—Assets reports, JQL+Charts, Atlassian Analytics?
Gotchas: Any schema pitfalls, performance tips, or permission quirks we should watch out for?
