PROJECTS | ||||||||
|---|---|---|---|---|---|---|---|---|
Column | ID | KEY | NAME | DESCRIPTION | CATEGORY | LEAD | URL | COUNTER |
Type | BIGINT | VARCHAR | VARCHAR | VARCHAR | VARCHAR | VARCHAR | VARCHAR | BIGINT |
Indexed | x | x | x |
|
| x |
|
|
...
How to get all the project issues? This is not possible per the JIRA,API design, There Given a JIRA project, there is not a straightforward way to get all its issues by using the JIRA Java API: there is not a Java method on the project object to get all its issues. The only way to get the project issues via API is by performing a JQL similar to:
project = SSP
SQL for JIRA is strictly driven by pure and strict wrap of the JIRA Java API and therefore : it follows the same pattern and it has the same constraints than the API. Therefore there is no way to get all the JIRA issues at once by using SQL as well as there is no way to achieve it by using JQL!.
If you try the SQL query below a full scan exception exception will be raised:
select * from projects p inner join issues i on p.id=i.projectid
even if you restrict the project to a single one:
select * from projects p inner join issues i on p.id=i.projectid where p.name='SSP'
...
select * from issues where JQL='project = SSP'
As you see, SQL for JIRA has respects the same constraints than JIRA constraints in order to limit to access to the resources and compromise the avoid to compromise the JIRA performance while and by keeping a the same good balance among features and performance.
...