Mindville has joined the Atlassian family!

Learn Insight for Cloud

Read the onboarding guide for Server and Data Center here

Your guide to Cloud success

What is Insight all about?

Onboarding introduction

Jira is great for managing your issues. And in practice, issues are often related to something or someone like a computer, a license, or an employee. That's probably why you installed Insight. This video introduces how you can use Insight and what you will cover in this Onboarding Guide.

Documentation:

Insight Overview

Installation

A quick step-by-step guide to installing Insight in your Jira environment. You must already have Jira for Cloud installed.

Steps to install Insight.

  1. Log in as a user with the Jira Administrator global permissions.
  2. Open the settings and select 'Apps'.
  3. Click 'Find new apps' from the left sidebar and search for 'Insight'.
  4. Select 'Insight - Asset Management'.
  5. Click 'Try it Free' to install the app. Note, if you have already purchased through the Atlassian Marketplace you may see 'Install now' instead.
  6. Click to start the free trial. Our subscription will start after the trial period unless you cancel your subscription before the trial ends.
Documentation:

Installation guide

Data Modeling

To ensure the best configuration of Insight, it is important to structure your assets properly.

Objects

In Insight, assets are stored as Objects. Each Object has its own set of attributes that define it. To make the organisation of these assets or Objects easier, Insight lets you structure your Object data with Object Schemas and Object Types. You can learn much more about how these work and how to create them in the videos below.

Documentation:

Objects

Object Schemas

Let's start at the beginning. You might want to manage different kinds of assets or objects. You can think of an Object Schema as a container for assets of a specific nature. For instance, you could have an Object Schema for IT assets, Employees, or even Customers.

Documentation:

Object Schemas

Object Types

Once you've set up a container, you want to be able to structure your assets inside your Object Schema. For this, you can use Object Types. An Object Type can be a specific kind of asset - like printers or computer screens. Or an Object Type can be a group of similar assets. For instance, printers and screens can be grouped under ‘Hardware’.

Documentation:

Object Types

Object Attributes and references

Once you've structured your assets, you need to define the information you want to collect for each of those assets. For instance, for computer screens, we might want to know the vendor, screen size, employee and price. You can also add reference type attributes which are used to define asset dependencies. That’s what Object Attributes are all about.

Importing

Get your data into Insight with the CSV import tool. We're working on more importers so keep an eye out.

CSV

If you're using a spreadsheet like Excel or Google that contains all your assets, you can use the CSV import to bring your data in Insight. This will ensure that you have an integrated and transparent system where you can link your assets to issues and analyze impact. This video guides you through importing data from a CSV file.

Documentation:

CSV Import

Jira Integration

This section shows you how to make Insight objects and their attribute information available on Jira Issues.

Integrating Insight with Jira

One of the biggest benefits of Insight comes from getting the correct asset information when and where you need it - i.e. in your Jira tickets. This video will explore what that looks like and how it can be useful. 

Configuring the asset field

Any object in Insight can be linked to issues. And any information about these objects can also be displayed on issues. For this, you need to use asset fields and custom fields. This video shows you how to configure this in Jira Cloud.

Documentation:

Insight asset field

IQL

Automation

Streamline your operations with automatic actions performed in Insight and Jira.

Automation rules

Automation rules allow you to perform actions automatically based on events that take place in Insight, following an IF-THEN logic. These actions include creating issues, sending notifications, executing scripts and sending HTTP requests. For instance, if a license approaches its expiry date, email the provisioning department.

Documentation:

Insight Automation

Post functions

Similarly to automation rules, post functions allow you to automate the execution of actions. The difference is that the actions take place when the status of an issue changes through a Jira workflow (Issue Transition). These actions include updating an asset, sending a notification and running a script. For instance, when an issue is created requesting the onboarding of an employee, assign necessary assets to the new user including laptop, cell phone and cell phone subscription.

Integrations

Use integrations to share data between Insight and other applications.

REST API

If you want to bring in data from specialized sources or want to use your Insight data in any of your other applications, you can do so with the REST API provided. To use the REST API, you must have a valid personal access token which you can get from the Configuration menu. More details are in the documentation.

Documentation:

REST API

Additional Learning

Additional information to take Insight to the next level.

Insight Query Language - IQL

Insight provides JQL functions that allow you to search and filter your assets. In practice, IQL can come in handy when you want to build search views, automation rules, or references between assets. This article covers those IQL functions.

Documentation:

Insight Query Language

Roles and permissions

A role is a set of permissions granted to Jira users or Jira groups to view or modify data in Insight. Roles can have three scopes - across all of Insight, for a specific object schema, or for a specific object type. You can use Roles to make sure people can only access the data that they need.

Documentation:

Roles and permissions