In STAGIL Assets, asset objects and CIs are derived from Jira issues. Users can efficiently search for assets and filter results using the default basic search or JQL.
For assets linked via advanced links, we provide additional JQL queries. See more here: JQL Search and JQL Variables
Assets Navigator provides an option to quickly search through your selected assets projects. Users can find a search bar in the top navigation panel. The search bar can be used for search by text or by JQL queries.
By default, the search bar is set to text search. To switch to JQL, simply click on the TEXT button.
Advanced JQL Search
Our app features a custom JQL search function that allows users to search for issues using Advanced Links, integrated directly into the Assets Navigator. This tool simplifies the input of query parameters, enabling you to find related issues quickly.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
Advanced Search panel is also available in Issue Search. Click on the Assets icon to open the dialog.  |
Let’s walk through an example to understand how this search function works.
Scenario:
A user wants to find all Invoice issues related to a specific Organization issue (in this case, issue key CRM-29). However, invoices are linked through Service issues, meaning they aren’t directly visible when viewing the Organization issue. Instead, user needs to search through related Service issues to find the relevant Invoices.
Here’s how we would set up the search, using our tool:
Start with the Search Node:
In the search dialog, enter the search node: key = CRM-29. This is the Organization issue you’re interested in. 
Search node can be a single issue or an issue array.
Enter the First Link Type:
To follow the connection between Organization and Service issues, enter the link type Available Services. This tells the search to look for Service issues linked to the Organization.
Enter the Second Link Type:
Next, enter the second link type Invoiced Via to trace the relationship between Service issues and Invoice issues. This ensures the search moves beyond the Service issues to find related Invoices.
Set the Link Level:
Since you’re searching across two layers of issue relationships (Organization → Service → Invoice), set the Link Level to Level 2. This tells the search to go two levels deep in the link structure. If you were to select Level 1, the search would stop at the Service issues, missing the Invoices.
Search result contain all issues that were linked to the starting search node (CRM-29). In order to narrow down the results according to the initial goal, user can add an additional JQL filter.
Add a JQL Filter:
In the JQL filter input bar (to the right from the dialog icon), add the query: type = Invoice. Without this filter, the search would return both Service and Invoice issues, as the links exist for both.
