Display all of a user's assets within a REQUEST FORM

[Eddie Ojeda]

We already have our user's assets linked to tickets. This is different.

The request form is for terminating an employee that their manager fills out. In one drop-down they select a user to be terminated. Now, I want a list/paragraph/etc. to display all the user's currently assigned assets.

I have not found a real way to do this because linking an assets object requires changing the field type to an assets object (which is a drop-down, not a visible list). The goal is for the manager to see which assets they are responsible for getting back to us (in IT). This also allows us to see the assets we should get back without having to look them up in Assets ourselves.

[Mikael Sandberg]

Hi @Eddie Ojeda,

Welcome to Atlassian Community!

You can do this by using assets object fields and filter issue scope. You could then have it set up so the manager picks the employee and by doing so the second object field can be filtered to only display assets that the employee is linked to. Have a look at this article for more information. 

[Eddie Ojeda]

I think the reason this is failing is because the manager fills out the form (making him the "reporter", right?), but I don't want to see the manager's assets. I haven't figured out how to tell it to use the name from the drop-down that shows the user to be terminated:

Filter scope (AQL): objectType = "Laptops"

Filter work item scope (AQL): Owner.User= ${reporter}

It also mentions using "customfield_10236" in their example but not how this info is found in my custom field.

[Mikael Sandberg]

Yes, you would need another field for the employee. I would add one called Employee that that is an asset object field and then use that to get the laptops. Of course this would only work if all employees are an object. If they are not then you can use the custom field. In Assets, how do you link a laptop object to the user? 

[Mikael Sandberg]

And no, customfield_10236 may or may not exist in your instance, that is just an example.

[Eddie Ojeda]

All employees are an object. Isn't this: "In one drop-down they select a user to be terminated" the same thing as an "Employee" field? Regardless, I don't know how to use this field to "filter" the other assets field to show only that employees assets. As above, those filters did not help.
I've also tried using custom fields, but having no luck; it just says "No options" when clicking on the drop-down.

I figured customfield_10236 was an example, but how do I find the actual customfield_##### for my custom fields?

[Henry Reeb]

The number will be at the end of the URL at the top of your browser.

[Eddie Ojeda]

Here's an example of the linking problem:

1. I select the Employee (populated via a custom field using a user group).
2. I click the drop-down at the bottom and it shows "no options" instead of listing all of the assets belonging to "James":



I wanted the items to just be displayed (in other words, a textbox, not requiring a click on its drop-down field). When I choose the user, immediately show all of that user's assets.

[Mikael Sandberg]

Okay, does your filter on the asset object look the same, just replaced reporter with the custom field? If the employee field is a user picker, what is being returned when you use it in the filter is the Atlassian Id, not the display name. Is Owner.User attribute the name of the user? If so then try changing the filter to look like this:

Owner.User = $(issue.customfield_XXXXX.displayName)

[Mikael Sandberg]

And if you want to display the returned result as just a textbox and not a drop down list that is not possible without an app from the Marketplace that can run a live script on the request form.

But if you are okay with adding the objects to the ticket after then you can achieve that with automation and either add the text to a separate custom field or the description. The drawback with using a custom field is that it cannot be displayed on the portal unless you link that field to a field in a form and attach the form to it. I created an article about it here.