How can I create a customer-facing browser for Jira Assets (formerly Insights)?

[Laura Bennett]

I have an object schema called Software Portfolio where each object represents a type of software used within the company. The object attributes include information about the software, such as a software description, the number of available licenses, the cost of the licenses etc.

The object schema is used and maintained by a group of service desk agents via Asset & Configuration management, but I would like to discover a way of allowing service desk customers to browse the portfolio in a read-only, user-friendly way, that doesn't consume a service desk license. 

For example: 

Andy wants to request a license for "Software A" but he's unsure if there are any free licenses available. He searches for "Software A" in a custom asset field and the corresponding attributes for that software, including number of available licenses, are displayed for him.

A more advanced example:

Andy needs to use a design software but he's not sure what design software options are available at the company. He searches for "Design" in a custom asset field and is shown a list of all objects where the word 'design' is present in the description attribute.

Has anyone been able to configure anything similar or can think of a possible solution?

[Line Lengfelder · Accepted solution]

From the top of my mind:

Create attribute to the software portfolio objects, for example "Workplace software" or something like that, if you haven't got an exisiting attribute you can use.

Add an attribute for "Software Category,, and add "Design" etc.

Then set a filter scope in the field context that shows

objectType = "Workplace software" AND "Available licenses" >= 1 

Allow search filtering by these attributes: Name, Software Category, Whatever

Then add the field to the request type.

That way the user can write "Design" in the portal field form, and get all the objects with that category that have free licenses.

Haven't tried myself - would love your feedback.

[Laura Bennett]

Thanks for the thoughtful reply. 

I've tested this approach and it does work for filtering the objects field so only software with available licenses are searchable to the user.

My issue is that the custom field in a raise a request screen isn't such an elegant solution when the customer doesn't want to raise a request but just wants to browse the objects in the database.
 
Do you have any ideas of how we could make the object field available to customers without them having to raise a request? I know they could just open the create request screen and then cancel once their done browsing but this isn't so intuitive.

[Line Lengfelder]

I don't know, but had to check Marketplace. How about something like this? 

Checkout - Procurement & Asset Manager | Atlassian Marketplace