Administration

Context and project configuration

Once the application is installed, it will be accessible to all users across the instance, including all projects and issues. Users will be able to view Issue Maps buttons and panels. However, if you wish to limit the app's appearance to specific projects or issues, you can do so by using Project configuration.

To start the configuration process, navigate to Manage apps → STAGIL Issue Maps → Project configuration. On the configuration page, administrators will notice that a default configuration has already been created and includes all project categories/projects/issues. This configuration controls Issue Maps on a global level.

Open

If you wish to create a more customized configuration, start by selecting the context in the fields ‘Project category’, ‘Project’ and ‘Issue Type’, and then click ‘Add’.

In the ‘Actions’ menu of the configuration → Manage.

Open

This page enables you to configure how users will view and utilize the Issue Maps apps within a specific context:

• Project Sidebar Icon: enables an Issue Maps link icon in the project’s sidebar

• Issue Graph Button: enabled an Issue Maps link icon in the issue navigation.

• Default Graph Level: select a level of issue links to display by default when the graph is opened (only for issue graphs)

• Default Issue types: issue selected to display in the graph by default (only for issue graphs)

• View Screen Issue Graph: adds an expandable Issue Map panel to the issue’s Activity or Side panel.

• Default Links Types: link types selected to display in the graph by default.

Quick Filters

The Quick Filter feature enables users to save frequently used JQL queries as a filter for quick access.

Issue Hierarchy

Use this feature to rearrange the hierarchy of your issue types and display them correctly in the asset graph. Simply click and hold on an issue type, then drag it up or down the list to its desired position. The issue types are listed in descending order, meaning that those at the top will be considered higher in the hierarchy than those below them.

In cases where asset issue types belong in the same hierarchy level, you can create a new level and map various issue types to it. To do this, select an issue type and click on the "edit" button. This will allow you to make changes to the issue type's properties, including its hierarchy level and create an issue level.

For example, a new level called "Devices" is required to include all smartphone, printer, and notebook issues in it. To do this, select each of these issue types and edit their hierarchy level to "Devices".