Overview

Datasources are the entities that securely connect your instance with the tools where your data is. For example, the default datasource is the instance where the app is installed, which needs no configuration.

This data is collected thanks to the integrations provided by the app (see Dashboard Integrations: Datasources for further information).

Datasources and gadgets

Each gadget uses a datasource, and several gadgets can share the same datasource. Initially, when you configure your first gadget in a dashboard, you can opt for having all the compatible gadgets automatically configured with that datasource. Imagine that in your dashboard there are four gadgets that use Bitbucket as datasource, when you configure the first one, the rest can be automatically configured with the same datasource.

See Add and Manage Datasources to see how to configure a datasource.

Access restrictions in datasources

Datasources fetch and display information from external products, which sometimes you may want to keep for yourself. In this case, you can configure access restrictions and avoid anyone else from using your datasources. You’ll find the following options to set up access restrictions:

  • My organization. Any logged in user in your instance can use this datasource.

  • Private. Only the creator of the datasource can use it.

This restriction can be set when you create the datasource, or accessing through the lock menu. It’s indicated with an unlock icon if My organization is selected and with a lock icon if Private is selected.

Type of datasources

Dashboard Hub uses three different types of datasources:

Default datasource

The default datasource is the Jira cloud instance where the app is installed, and it is called the default datasource. You won’t need to configure anything else. This datasource retrieves the data from the current Jira cloud instance. The main characteristics are:

  1. It is enabled by default, no need for further configuration. It can be selected right away in compatible gadgets.

  2. It has access to the Jira cloud instance where the app is installed.

  3. Data access and permissions are the ones of the user who created the dashboard (dashboard owner). Thus, users have the very same permissions that they have in the Jira instance.

Connector app

The Dashboard Hub Connector app is a special app that you install on some Atlassian cloud products like Jira (Core, Software, Service Management), Confluence and Bitbucket (includes Pipelines).

This app is a bridge to bring data from others other Atlassian products, keeping users and security privileges configured on every instance. This means that users can access data from other Atlassian cloud products only if their Atlassian accounts have the right and sufficient privileges.

Thus, it is possible to grant access to other datasources in a fast and easy way, while maintaining data security without additional configuration. The main characteristics are:

  1. Data access managed on and by each Atlassian Cloud product instance.

  2. It just requires an admin to install the app and you are ready to go!

  3. It requires Dashboard Hub for Jira (paid app) to be installed in the main instance, but the Dashboard Hub Connector apps are free apps!

API Token

This type of datasource is required when the source of the data does not allow to install a connector app. In this case, you need to provide a user name and an API Token, so that the app can access and retrieve the information from these external sources. This mechanism is pretty common for integrations with third party vendors, and sometimes with Atlassian products too.

This API Token is stored in your Jira cloud instance as an entity property and encrypted using AES to keep it safe from crooks.

So, the API Token allows retrieving data from services and tools like the Atlassian Marketplace, Opsgenie, Statuspage (all avaiable today), and others available soon like maybe HubSpot, ServiceNow, Zendesk, Pipedrive… (see Dashboard Integrations: Datasources). The main characteristics are:

  1. It provides data access to several third party products and services.

  2. No need to install extra apps, just the API Token.

  3. The access is limited by the API Token. It will just allow to retrieve the data allowed by API Token.

See also