IssueAffectedVersions
Query the Affected Versions of an issue in JIRA.
Table Specific Information
You can search IssueAffectedVersions by using SQL and JQL (JIRA Query Language).
Select
The driver uses the Jira API to process some of the filters.
The driver processes other filters within the driver. You can turn off the client-side execution of the query by setting SupportEnhancedSQL to false.
The available columns for IssueAffectedVersions are IssueId, IssueKey, and JQL. For example:
SELECT * FROM IssueAffectedVersions WHERE IssueId > 10022 AND IssueId < 10090
Columns
Name | Type | References | SupportedOperators | Platform | Description |
VersionId [KEY] | String | =,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN | Common | The Id of the affected version. | |
IssueId [KEY] | Integer |
Issues.Id | =,<>,>,>=,<,<=,IN,NOT IN | Common | The issue Id of the affected version. |
IssueKey | String |
Issues.Key | =,<>,>,>=,<,<=,IN,NOT IN | Common | The issue key of the affected version. |
IssueCreatedDate | Datetime | =,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN | Common | The date the affected version's issue was created. | |
IssueUpdatedDate | Datetime | =,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN | Common | The date the affected version's issue was last updated. | |
Name | String | Common | The name of the affected version. | ||
Archived | Boolean | Common | A boolean indicating if the affected is archived. | ||
Released | Boolean | Common | A boolean indicating if the affected is released. | ||
ReleaseDate | Date | Common | The release date. |
Pseudo-Columns
Pseudo column fields are used in the WHERE clause of SELECT statements and offer a more granular control over the tuples that are returned from the data source.
Name | Type | Description | |
JQL | String | JQL (JIRA Query Language) allows you to build structured queries. |