Assets Procurement
https://stagil.atlassian.net/wiki/spaces/SAJC/pages/850100386 can help you turn spaces with work items into a dynamic, searchable asset catalogues.
Instead of selecting options from a static dropdown, users can browse through actual Jira work items that represent your assets, with you fully controlling what information is shown to the customer.
What do customers see?
When a user opens a request form in the customer portal, they’ll see an Advanced Link field representing available assets.
Instead of a basic dropdown, a catalogue-style dialogue opens, displaying each laptop with its brand, specifications, and price.
Users can immediately compare options, much like browsing products in an online store.
If the customer prefers a more visual experience, they can switch to the grid view using the button in the top-right corner.
In this layout, each asset is displayed as a card with an avatar, short summary, price, and status.
Each card or table row can include additional metadata, such as screen size, dimensions, or operating system, depending on the fields defined by the administrator.
To help users find what they need, the dialogue includes both text and JQL-based search.
Customers can filter results by any field, e.g. by model name, status, or RAM size.
After customers have selected and confirmed their assets, the total price is automatically calculated and displayed in the request form, giving them a clear overview of the estimated cost before submission.
Everything a customer sees, the displayed fields, filters, and available assets, is fully defined by the administrator. Only assets that meet your chosen JQL filter appear (for example, status = Available), ensuring users never see items that are retired, reserved, or restricted.
What do agents see?
When an agent opens a submitted request in the work item view, they see an Advanced Link field panel listing all ordered assets.
Each asset appears as a row in a table with details such as model name or price, providing a clear overview of what the requester has ordered. The details that the agent sees can be completely different from what the customers see: admins can configure a custom set of columns to match every use case.
On the far right side of each row, there’s a marketplace icon. This icon acts as a button and is the main control an agent interacts with to process each asset request.
After reviewing the ordered assets, the agent clicks the marketplace icon next to the asset they want to process. This dialogue functions as a Create asset form. It automatically uses the selected model as a template for generating a new, specific asset record. In the dialogue, the agent needs to provide a name for the new asset, i.e. a summary for the new work item that will be created.
If needed, admins can configure additional fields to be displayed on the form:
When the agent clicks Add, a new work item is created automatically.
This new record uses the same work item type and fields data as the original model but now includes the newly entered serial number and purchase date.
The app then performs the following updates automatically:
The original model that was linked to the request is unlinked.
The newly created asset (with the serial number and date) is linked in its place.
The marketplace icon in the table changes to a check mark, signalling that the asset has been processed and provided.
At this point, the request reflects the actual assets assigned to the requester.
All created asset records remain linked to the procurement request, ensuring full traceability between what was ordered and what was delivered — without any manual linking or duplication work by the agent.
Learn more about the configuration of this feature here: https://stagil.atlassian.net/wiki/spaces/SAJC/pages/3350396962