Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Create select box custom field where source Asset attribute is an Object array

Joe Biland June 3, 2025

In our Asset schema, we have 2 object types:

  • Applications
  • Application_Roles

 On the Application_Roles object we have defined multiple application roles:

  • Administrator
  • Developer
  • Customer
  • Member

On the Application object:

  • we created an attribute named applicationRole 
  • this attribute is type = Object 
  • this attribute references the Application_Roles object.

We have 4 applications defined in Applications:

  • Atlassian - Confluence
  • Atlassian - Jira Software
  • Atlassian - Jira Service Management

We have tagged the applicationRole on each of the above Atlassian applications (Confluence, Jira Software, JSM) to include three selections

  • Administrator
  • Developer
  • Customer

We create a custom field to allow for the selection of an Application:

  • Filter scope (AQL): objectType="Applications"

We created a second custom field intended to list available application roles

  • Filter scope (AQL): objectType="Applications"

  • Filter work item scope (AQL): Label IN (${customfield_10208.label${0}})

  • Allow search filtering by these attributes: applicationRole

The result is that we have the second custom field return the Application Roles, but

  • the results are in a comma delimited single value "Administrator, Developer, Customer"
  • when this single value is selected, the Application Name is populated in the select box 

Our desired outcome is a select box with each Application Role as a selectable option. 

We do NOT want a complete separate table referencing a 1:1 application to individual role if at all possible.  Curious if there is a trick to reading this multi-value attribute on a record to create a drop-down select box with each value listed separately.


Thanks in advance. 

1 answer

1 vote
Joe Biland June 3, 2025

We have determined a working solution.  We set the second custom field to use objectType = Application_Roles for Filter Scope, then used the following for the Filter issue scope (AQL):

object having inboundReferences(objectId IN (${customfield_10208.id${0}}))

This resulted in this second custom field starting from the roles listing and filtering it based on inbound references associated with the custom field ID of the Application selected.

 

We are now seeing individual roles listed for selection in this second custom field.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events