Let's say your company is a heavy JIRA user. You have tens of projects and they are divided in two categories - Internal (where you track issues internally) and Service Desks (where people from outside the company report issues). All of the issues across all projects are synced in one data source jira_issues.

If you need different insights for internal projects and service desk projects you would use the following SQL for internal projects:

SELECT * FROM jira_issues WHERE projectname like '%Internal%'

and for service desk projects:

SELECT * FROM jira_issues WHERE projectname like '%Service Desk%'

You'll have to repeat this operation across all insights that separate the two types of issues. And if it happens that you change the naming convention of the projects you'll need to go over all of them and fix this.

By creating a Virtual data source for the two types of projects you can control this from a singe place. 

Create new Virtual Data source for the internal projects. Give it a key internal_jira_issues. As SQL use the first example:

SELECT * FROM jira_issues WHERE projectname like '%Internal%'

Create another Virtual Data source for the service desk projects. Give it a key service_desk_jira_issues. As SQL use the second example:

SELECT * FROM jira_issues WHERE projectname like '%Service Desk%'

From here on in your insights when you want to use either type of issues already filtered just use:

SELECT * FROM internal_jira_issues

or

SELECT * FROM service_desk_jira_issues


 

Did this answer your question?