This documentation is for Insight for Server/Data Center only.

The Default Insight Custom Field can handle dependencies for more the one parent, please check it out.

Say goodbye to old cascading selects, multi cascading selects or what ever kind of cascading fields you've used in the past. Say hello to the new Referenced Insight Custom Field. Here is how you unleash the power of really deep dependencies.

Choose Single Select or Multi Select

The Insight referenced custom field comes in two flavours, single select and multi select.

single select custom field is used when you want to restrict the possibility to associate only one Insight object to each Jira issue. Configuring the Insight single select custom field will prevent users from associating more than one Insight object to each Jira issue.

multi select custom field will allow the user to associate unlimited number of Insight objects to each Jira issue.

Create the Insight referenced custom field

  1. Login as a member of the Jira-administrators group.
  2. Navigate to Custom Fields in the admin section of Jira. 
  3. Click Add Custom Field and select Advanced
  4. Select the field type Insight Referenced Object (single select or multi select)
  5. Give your Insight Object Field a Name and a Description
  6. Associate the custom field to the desired screens

Configure the Insight referenced custom field

  1. Locate your Insight custom field and click on the cog icon  and select Configure
  2. Click on the link "Edit Insight Configuration"
  3. Select the parent custom field where selected object/s will be used to search for references.
  4. Select which direction the references should apply. Outbound references are all references that are set on the object/s attributes of type 'Object'. Inbound references are all references from other object/s that reference to the selected object/s. 
  5. You can restrict this custom field to just show Jira User related objects. Logged in Jira User will only see the objects where the User is related to. Insight fetches on User type, Group type and Email default type attributes. To restrict an object where a referenced object has a specific user connected (reference deep more the one), you can use an additional IQL. See section 8 below.
  6. You can restrict this custom field to just show project related objects. Users will only see the objects where the current project is related to.

  7. You can specify which reference types to be fetched. Leave this field blank to choose 'All reference types' if you want all reference types to apply.
  8. You can filter objects on attribute values to make the selection of objects to fit your specific needs. An example could be:

    Status = Active

    Read more about IQL here.

  9. In the create/edit view and in JIRA or Customer portal, you can filter objects on attribute values additional to the IQL mentioned in bullet 8. This selection does not apply in any JQL search. An example could be:

    "System Owner".User = currentReporter()

    Read more about IQL here.

  10. You can specify the attributes to filter on, this field is mandatory and at least one has to be configured. Label is default.
  11. You may also specify which attributes should be visible in the JIRA Issue/agent view for any objects attached the an issue.

  12. For JSD configuration; You may specify if object picker should be available on the portal

  13. For JSD configuration; You may force to show/hide the customfield on the customer details, even if not placed as visible request field.


On this page: