Utilize an external list in Jira using a Key/Display value pair

[RandomJoe]

We have data external to Jira that has a Key ID column and a Display name column. The Key value is guaranteed to never change but the Display value could change over time.

We want the user to see the user to work with (view/update) a record based upon the Display value, but we want to store the Key value.

If the Display value should change we want Jira to use the Key value to lookup the correct Display value and show that to the user.

• For example, a department Key of 10247 with a Display name of "External Relations" is later changed to "External Affairs"

How can this be done in Jira? Do we have to maintain two custom fields and use scripts to keep them in sync? Is there another tool or technique that can be used?

[Joshua Sneed Contegix · Accepted solution]

Hi RandomJoe,

You will likely need something to reach to the external data store, pull it into Jira, and format it in a useful manner. You could develop a one-off solution or use a plugin like Elements Connect, Insight for Jira, or Scriptrunner. They can reach out to various data sources (slightly different between each plugin) on a schedule and surface that data through a custom field. Cheers!

[Julie d_Antin _Elements_]

Thanks for suggesting Elements Connect @Joshua Sneed Contegix 

@RandomJoeElements Connect live fields would do just what you're looking for. Could you detail how/where your data external to Jira stored? For example, in an SQL database?

[RandomJoe]

Yes, the data is stored in a SQL Server database. The resulting object may be a view, but it is a table at present. Multiple columns but the two I'm interested in are the DEPTID and the DEPT_SHORT_NAME columns.

Once again the DEPT_SHORT_NAME can change over time, so how does Elements Connect help with that?

Also, what would be the needed changes to Jira? Are we talking one custom field, a cascade field, two custom fields?

[Julie d_Antin _Elements_]

Elements Connect allows you to create custom fields that fetch data from external data sources, SQL databases being one of them. You can create live fields, which  get data from their datasource when they are edited and displayed, meaning you have real time data.

Since Elements Connect allows you to save a key related to your query but display different information, you could have just one custom field "Department" that allows users to select a department. With the live field configuration, the name of the department will always be up to date.

Elements Connect can also be used to create dependent cascading fields, so for example a second custom field that only displays employees/assets/etc for the department selected in the first custom field.

If you want to see more:
https://marketplace.atlassian.com/apps/23337/