Assets on portal
Connecting your Jira Assets database to the portal bridges the gap between physical equipment and digital support. By displaying asset fields in the request view, users can see the specific details of the hardware or software linked to their ticket—from serial numbers to warranty dates.
Why it’s a win-win
For customers: It’s a complete record. If they are reporting a laptop issue, they can see all the specs of their device right there on the portal, ensuring they’ve selected the right item.
For agents: It provides instant technical context. Agents don’t have to jump into the Assets schema to see the device details; they appear right on the request, ready for action.
How to configure it
Advanced edition
This field is available in the Advanced edition of Feature Bundle. For more details about app editions, visit this page.
In the Additional fields panel settings, select which Asset field to display. Below, we provide examples of fields that can be selected:
- Consumable Asset
- Current SW Asset(s)
- Employee Asset(s)
- Facilities Asset(s)
- Reporter Asset(s)
- Requested Asset
- Asset Status (single-choice field)
- Asset Tag (plain-text only field)
Edit Assets on customer portal
This field can also be made editable. This allows the user to update their asset details directly through the portal if something has changed (like a new office location). Learn more here.
Placement tips
This works perfectly in the center for detailed equipment specs or the side panel for a quick summary.
Why it works in practice
In a “Hardware Refresh” scenario, a user can see their current assigned laptop on the portal. If the details are wrong, they can use a customer action to edit the asset info. This ensures your Jira Assets database stays clean and your customer portal stays accurate without any manual agent cleanup.