How to configure Insight custom fields as cascading select list

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Purpose

To configure Insight custom fields as cascading select list

Example

Based on a schema with object types below,

You would like to have 2 custom fields on a request form to allow users to

  • Choose an Author object in the first field
  • Choose the Book object(s) in the second field. The options in this field should be based on the selected value in the first field.

Solution

There are 2 solutions with different combinations of Insight custom field types

Using an Insight custom field and an Insight referenced custom field
  1. Create a default Insight custom field for users to select author with the configurations below.
  2. Create a referenced Insight custom field for users to select books written by the author chosen in the custom field above. For this example, we select the field type that allows multiple option.


  3. Make sure both the custom fields are added to the right request type and test it out.

Using two Insight custom fields
  1. Create a default Insight custom field for users to select author with the configurations below.
  2. Create another default Insight custom field with the configurations below.

    Tips on constructing the filter issue scope

    How to construct the IQL?

    View one of the Author object and check the graph. Locate at least one of the objects that is expected to show up as an option and see the direction of the arrow. Is it pointing towards or away from the chosen Author object? In this example, they are all pointing towards the Author object and hence, we are looking for object having outbound references of Author. And to make sure only Book objects are showing as options, we add the condition for object type in the IQL.

    Why "Key=${Author}" instead of "Label=${Author}" or "Name=${Author}"?

    The value returned from the Author custom field is in object key format and hence, it needs to be matched using key.


DescriptionHow to configure Insight custom fields as cascading select list
ProductInsight - Asset Management
Last modified on Nov 4, 2021

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.