Create custom "Select" field that populates object attributes as options to choose
Asked by Garrett Richardson:

#### Scenario: {#toc-hId-318113395}

We are creating a request type that would allow technicians to create a new hardware record (object) after the request proceeds through an approval process to check for any glaring errors.

We do not want to allow technicians to create records on their own due to the possibility of straying from naming conventions and other data cleanliness concerns. Because of that, many attributes within the hardware record (object) are *Select*type attributes with options entered and maintained by a separate team.

That said, we **do** want technicians to be able to essentially "stage" a hardware record (object) for creation by filing the request. Once filed, using Automation, we then create the object once the request has been reviewed/approved and resolved at the end of the workflow.

*** ** * ** ***

#### Question: {#toc-hId--1489341068}

Is it possible for a custom field to populate (as selectable options) the options within a *Select* type attribute of an Object Type?

*** ** * ** ***

#### Example: {#toc-hId-998171765}

The technician needs to create a laptop object under the "Hardware" Object Type.

Within the "Hardware" Object Type is an attribute for "Model". That attribute is a *Select* attribute with a list of laptop models already created and maintained.   

Ideally, in the request, a custom field (dropdown) would be setup in which the options available to select are the options from the "Model" attribute of the "Hardware" Object Type.

*** ** * ** ***

#### Current Workaround: {#toc-hId--809282698}

We are currently working around this unknown by creating a custom Jira field for each attribute needed in the hardware record (object). The custom field (dropdown) has the same options as the associated object attribute. Through our automation we're able to read from the custom Jira field and then edit the Asset attributes accordingly upon creation. The automation works splendidly, the record is created and attributes assigned accordingly.  

Though, because of this approach, we have to essentially maintain two lists for each attribute.   

Pro: Clean / sanitized data.   

Con: Maintaining two lists for each attribute and running the chance of one list not being updated accordingly.

*** ** * ** ***

#### Current Setup: {#toc-hId-1678230135}

* This solution will be implemented by a Jira / Jira Service Management Administrator with Project Administrator rights for the project housing the request and with write permissions to the schema in question.

Thanks for any help you can provide.


Answers:
author: Mikael Sandberg
body: This can be done, but you would have to move your attribute out from the hardware object and make it its own object and then use a reference to it in the hardware object. You can then use an assets field for the user to select the attribute. If you take a look at the IT Asset Management schema you will see an example of it:

![Screenshot 2024-03-07 at 3.05.41?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/310943i2D9A760D362AFC0A/image-size/large?v=v2&px=999 "Screenshot 2024-03-07 at 3.05.41?PM.png")

In this template the Model name is a reference to the Hardware Models object.

comments: author: Garrett Richardson
body: That makes sense. Wish I had thought of that earlier!

Thanks, Mikael!


Tags: cloud

jira-service-management

jira-service-management-cloud