How to look up values in a field in another issue type to use as drop down field options for custom
Asked by Sean Campbell:

I have an instance with 6 Issue Types, there are common fields that are in all, most or some of each Issue Type. For Example, I have a field called:

OEM Name

This is in all Issue Types, but the OEM Name data is input first in the Customer Issue Type as this Issue Type is created first. Since I already have the OEM Name, in all other issue types that have the OEM Name field, I would like to do the following:

Create a Custom Field called OEM Name, as a pick list field. But the field options would use a LookUp query to get the OEM Names in Customer Issue Type OEM Name field (which is a Single Line Text field in the Customer Issue Type).

This way when users need to update the OEM Name in all other Issue Types, the pick list options show all of the OEM Names that have already been added to the Customer Issue Type record set.

My JIRA Team is not sure how to implement this, but I have seen questions that are similar for automatically updating Custom field values based on LookUp. This would execute the same as the Assigned Field when choosing who to assign an issue. You would begin to type an OEM Name and it would show you all the OEM Names in the Customer Issue List record set that match the letters being typed.

---EDITED CONTENT---

I am adding in a view of what I am looking for here:

![LookUp_JIra.png](https://community.atlassian.com/t5/image/serverpage/image-id/341593i4051F367B928347B/image-size/large?v=v2&px=999 "LookUp_JIra.png")

The shared field in both Customer and Model is the NAME FIELD, this assumes 5 records (5 different Customer Names) have been input into the Customer Issue Type. When creating a record in the Model Issue Type, I want the Name field in the Model Issue type to lookup the records in the Name Field in the Customer Issue Type and use the existing records as options for the user to select from for the Name field in the Model Issue Type,

This would not be external data, but data internal to the Jira Instance.

Hope that helps.

Thanks in Advance.

Sean


Answers:
author: Thomas Opiolka
body: Hi Sean,

I'm not entirely sure if I've understood your use case completely, but from what I understand, the "[External Data for Jira Fields](https://marketplace.atlassian.com/apps/1219994/external-data-for-jira-fields?hosting=cloud&tab=overview)" app might be a fit for your needs. This app can use your [Jira instance as a data source](https://documentation.codefortynine.com/external-data-for-jira-fields/local-jira) to retrieve all the OEM names from the Customer Issue Type, by using a JQL.

You then have a couple of options: you can use "[Field Option Sync](https://documentation.codefortynine.com/external-data-for-jira-fields/field-options-sync)" to periodically synchronize with a native select list of your choice, or you can employ the "[Extension Search Field](https://documentation.codefortynine.com/external-data-for-jira-fields/setup-a-search-field)" to fetch the data in real-time.

I should mention that I am collaborating with the vendor of the app I recommended.

I hope this is helpful nonetheless,

Thomas

comments: author: Sean Campbell
body: Thomas,

Let me check this out and I will come back to you.

Thanks!

Sean


Tags: cloud

jira-server