Overview

The ISSUES table is empty. It works in a similar way as the JQL table, but most of the ISSUE fields are available as columns, It accepts a JQL query in the ISSUES.JQL column to populate the table in real-time.

Performance

We are going to start with a common mistake. Most of the users might want to perform the query below for quick testing of the app:

SELECT 
 *
FROM
 ISSUES 

BUMP!. You will get the following error message:

Why? SQL+JQL driver is ready for large Jira instance and Data Center having millions of issues. The query above simply have does not sense. We name it as a user's reckless query.

This kind of queries can compromise the Jira reliability and cause serious performance problems in production. Fortunately, SQL+JQL Driver is enough smart and analyzes how the table indexes are used by the query.

An index in SQL+JQL means that the column is supported by the underlying Atlassian's API in a straightforward way. Without those input data, it is not possible to invoke the Atlassian's  API, then the query is aborted showing the expected data by the Atlassian's API.

The error message above means that one of these singe columns (ID, KEY or JQL) must be provided to populate the table. Usually, they are provided via conditions in the WHERE clause or table JOINs conditions:

SELECT
 * 
FROM
 issues 
WHERE 
 id = 10000 

This query above will show the fields of the issue with id = 10000.

The id condition does not have quotes because it is a numeric (integer) value.

Internally, the SQL+JQL Driver will get the issue id from the WHERE condition and will use it to invoke the Atlassian's API. This query will be performed very quickly taking very few milliseconds. 

Security

SELECT
 * 
FROM
 issues 
WHERE 
 jql = 'reporter = currentUser()' 

The query above is really very interesting.

The JQL string (note that is enclosed with single quotes as expected by the standard SQL language) will be performed by the app by invoking the Atlassian's API and the Jira results will be coveted into the SQL record format with strong support for data types (string, numeric, dates, ...)

You are seeing the transformation of Jira JQL query into SQL records!.

Another interesting issue: Who is the currentUser()? this is very subtle concept. Of course, it is the logged in Jira user as you supposed. But, the currentUser() is a Jira concept and databases are not aware of it. However, SQL+JQL Driver is always able to get the logged user in Jira  (it runs under a sort of automatic and transparent Single Sign-On) and the query is performed against the Atlassina's API taking it in consideration to preserve the Jira data privacy and respecting Jira permissions under any circumstance: SQL+JQL runs in the context of the calling user.... always!

This is a feature supported in the core of the app regardless of the tool used to run the query and there is no way to bypass it. The app will always return data checking the logged in Jira user's permissions. If no logged-in user could be found, the Driver will return empty no records. Anonymous access is not supported.