Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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 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 uses Bitbucket as datasource, when you configure the first one, the rest are also configured with that datasource. Not to mention that you can edit that configuration at anytime.

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

Ronin Dashboards 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 Ronin Dashboards Connector app is a special app that you install on some Atlassian cloud products like Jira (Core, Software, Service Desk), 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 data sources 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. Just requires an admin to install the app and you are ready to go!

  3. It requires Ronin Dashboards for Jira (paid app) to be installed in the main instance, but it’s a free app!

API Token

For this kind of data sources, you need to provide a user name and an API Token, so Ronin Dashboard will use them to access external resources (it can be from other Atlassian products or any other provider).

This API Token is encrypted stored by Ronin Dashboards in your Jira Cloud instance, keeping safe from bad boys.

On this way, you will be able to create dashboards retrieving data from any external resources like Atlassian Marketplace, Opsgenie, … or maybe HubSpot, Pipedrive, and many more (not yet, but soon).

Main features:

  1. Data access to several different external resources.

  2. You just need your API Token, which only will be used by Ronin Dashboards to retrieve any data that you want (and you can access).

  3. Access limited by the API Token: Ronin Dashboards will be able to obtain the data that the API Token allows.

See also

  • No labels