Is there a way to add extra identifiers to select field options?

Rando Tomingas
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 22, 2024

Hi!

I'm using both Jira and an external issue tracking system.

In Jira I'm using

  • Custom Select List fields (single choice) in my project.
  • Automation to send an HTTP request on updating and issue to pass on changes to the external system

In the external system I'm:

  • Periodically sending requests to Jira's Create custom field options (context) endpoint to keep the select field options up to date
  • Also periodically sending requests to remove out-of-date options

 

The data from external source looks like this:

[
{
"ProjectId": "project_id_1",
"ProjectName": "Project 1"
},
{
"ProjectId": "project_id_2",
"ProjectName": "Project 2"
}
]
The problem I have is that ProjectIds are not really human readable, but Project Names can at times be NOT unique, so I would need to somehow also associate the ProjectId with the ProjectName, so that when Jira automation sends the HTTP request with the the fields from the issue, I could in the external system see ProjectId instead of Project name.
Is there a way this could be achieved, so that when looking at the issue in Jira, people would still see ProjectName in the dropdown, but the system would save ProjectId as the value?
P.S. The amount of requests I send when creating the options for the select field does matter a bit, that's why I opted for creating the custom field options (context) API endpoint.

1 answer

0 votes
Thomas Opiolka
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 23, 2024

Hi @Rando Tomingas ,

Maybe consider a different approach: using the "Extension Search Field" feature from the third-party app "External Data for Jira Fields." This allows you to use a native search field type that stores both the value and ID directly in the field, making it accessible for JQL queries later.

The only limitation is that the values must be accessible via a REST API endpoint or database to perform the search. Hopefully an option worth the look?

Please remember, the marketplace offers additional options that might suit your needs, which you can find through a search. I should mention that I am collaborating with the vendor of the app I recommended.

Best regards,
Thomas

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events