Asset Groups & Filters

When you add a project to the Assets Navigator sidebar, you'll find a straightforward two-level structure: the project and its issues.

For more detailed project overviews, STAGIL Assets offers two more hierarchy levels:

• Assets Groups

• Assets Filters

Asset Groups

Assets groups allow the creation of an additional hierarchy level between project and issue.

For example, a CMDB project has just been added to the Assets Navigator:

Open

Default project view in Assets Navigator

To simplify navigation, issues in the project can be grouped together. For instance, the issue types Monitor, Notebook, Smartphone, and Periphery are collected under the common folder 'Hardware'.

Open

Project view with a configured Asset Group

Configuration

To group issues within the project, hover over the project title in the navigator’s sidebar to reveal the (···) icon. Click the icon to open the menu and select ‘Create group’.

Name the group and select the issue types to include in the group. Click ‘Create’

Asset Filters

Asset filters allow the grouping of assets based on custom field values and then display such groups in the Sidebar.

The following use case provides a clear and practical explanation of this feature's benefits.

Use case

Pre-condition: a CMDB asset template is in use.

Requirement: provide users quick access to an overview of active and inactive Applications. Users should be able to get a list of assets filtered by status.

Resolution: Create an asset filter for the Application issue type. The filter link is accessible directly in the Assets Sidebar, displayed as a sub-folder of the Application listing.

Creating a filter

To create a filter, hover over the issue type and click on the revealed three dots icon:

Select ‘Create filter’ to open the configuration dialogue:

Filter Configuration

Name. This is the title displayed in the Assets Sidebar.

JQL. A JQL query.

In our example, we will filter our Applications by status; hence, the JQL query is status = Active.

By default, this query already automatically includes the context condition project = X and type = Y
In this use case, project = CMDB and type = Application.Thus, it is not necessary to include in the filter JQL.

Result

A tab with the title ‘Active’ appeared in the sidebar. The tab is positioned as a sub-level of the ‘Application’ tab.

By clicking on the ‘Active' tab, users can view all 'Application’ issues that are currently in the 'Active' status.