Our Advanced Links fields can be used as cascading select lists, similar to the default select list cascade in Jira. This feature enables dynamic filtering based on the relationships defined by Advanced Links. It allows users to select a value in one field, and then filter the selectable options in a subsequent field based on the value selected in the first field (parent field).
Unlike other filters in Jira that may be based on JQL, the filter applied here is based on the Advanced Link type.
Let's consider a practical example to understand this better.
Example: Organization -> Product -> Service
We have three issue types: Organization, Product, and Service.
Organizations purchase products.
Products are associated with specific services.
Organizations have access only to services associated with the purchased product.
Each organization is linked to its owned products via an advanced link, and each product is linked to its available services, also via an advanced link.
Scenario
As an account manager, you want to view the products linked to an organization and then filter the services available for those products. For instance, you have the following setup:
Organization: AMW Corp
Product: MailMaster Pro
Service: Various services linked to MailMaster Pro
In the organization issue view, you only want to see the services linked to the product "MailMaster Pro" in the "Services" field.
Step-by-Step Configuration
Navigate to Advacnced Link field configuration: filter is configured in the ‘child’ field on the cascade. In our example, this is the "Available Services" field:
Set up Parent Field filter: In the "Parent Field Filter" tab, you will configure the filter using three select lists.
Parent Field: Select the field that represents the parent issue. In this case, select the field for the product, which would be "MailMaster Pro."
Link Types: Select the link type that connects the value in the parent field (product) with the results you want to see in the filtered select list (services). For example, choose the link type that connects "MailMaster Pro" to its available services.
Link Level: Choose the depth of the filter. This allows you to specify how many levels deep the filter should go to find the linked issues.
Example Configuration
Organization: ABC Corp is linked to the product "MailMaster Pro."
Product: MailMaster Pro is linked to several services via advanced links.
Service Field Filter Configuration:
Parent Field: Product (MailMaster Pro)
Link Types: Select the link type that connects MailMaster Pro to its services.
Link Level: Select the appropriate level (e.g., Level 1 for direct links).
By configuring the field in this manner, when viewing the organization issue (ABC Corp), the "Available Services" field will display only the services linked to the selected product (MailMaster Pro).
Benefits
Dynamic Filtering: Filters options based on advanced link relationships, not JQL or custom field values.
Improved Data Management: Ensures that only relevant and linked issues are displayed, reducing clutter and improving accuracy.
Enhanced User Experience: Simplifies the process of selecting related issues, making it more intuitive for users.
Conclusion
Using Advanced Links as cascading select lists provides a powerful way to manage related issues in Jira. By following the steps outlined above, you can configure your fields to display only the relevant linked issues, enhancing your issue tracking and management capabilities.
If you have any questions or need further assistance, please refer to our support documentation or contact our support team.
Our fields can also be used as cascading select lists. except that when and issue is selected as a values in such a select list, then it is linked to the current issue (aka in issue view of which the select list advacned link field is displayed)
So the usage of our advacned links as cascade is similate to the default select list cascade. Given that we have 2 fields, user selects a value in the first. And after that he can select a value in the second field, because the selectable options in the second field are filtered based on what values was selected in field 1 (or parent field)
Since the cascade is based on advacned links, the filter applied to field 2 is also based on the advanced links, and them only.
This is best explained on the following example:
We have 3 issues types: Organization, product & service.
Orgs buy products, and then entitled to a specific services available for that specific product. Each org is linked to an owned product via adv link and the product is also linked to a service, also via adv link.
As a org account manager, in the org issue view i can only see linked products. And I have an empty available services field in which i want only to see services linked to my product.
For this we create a filter for the available services field: go to this field configuration, ‘parent field filter' tab.
In this tab, we have 3 select list to configure the filter
Parent field: here we would select a field, a linked issue of which we would be using a first node for our filter. In our case such value would be a Product ‘MailMaster Pro’
Link types: here we would need to select a link type that connect the value in the parent field with the results that we want to see in the select list after filtering.
Link level: allows to select the depth of a filter.