PROJECTS | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Column | ID | KEY | NAME | DESCRIPTION | CATEGORY | LEAD | URL | COUNTER | ISARCHIVED | ARCHIVEDBY | ARCHIVEDON |
Type | BIGINT | VARCHAR | VARCHAR | VARCHAR | VARCHAR | VARCHAR | VARCHAR | BIGINT | BOOLEAN | VARCHAR | TIMESTAMP |
Indexed | x | x | x |
|
| x |
|
| |||
...
How to get all the project issues? 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:
...
As you see, SQL for JIRA respects the same constraints than JIRA in order to avoid to compromise the JIRA performance and by keeping the same good balance among features and performance.