IssueFixVersions

Returns the list of versions in which specific issues are expected to be resolved.

Table Specific Information

You can search IssueFixVersions by using SQL and JQL (Jira Query Language).

Select

The connector uses the Jira API to process some of the filters.

The connector processes other filters within the connector.

The available columns for IssueFixVersions are IssueId, IssueKey, and JQL. For example:

SELECT * FROM IssueFixVersions WHERE IssueId > 10022 AND IssueId < 10090

Filtering with IssueId comparison operators

Due to limitations in the Jira API, filtering with comparison operators on the IssueId column (>, >=, <, <=) only works reliably within the context of the project that contains the specified issue. To improve behavior, the connector transforms these comparisons into equivalent filters on the IssueCreatedDate column by resolving the Created datetime of each referenced issue.

This transformation is applied only when the KeyColumnOperators connection property is set to "Server-Side" (the default). In rare cases, connector may assign a higher IssueId to an issue created earlier, which can result in incorrect filtering when relying solely on IssueId comparisons. For fully accurate results across all projects, set KeyColumnOperators to "Client-Side". This mode retrieves the entire issue dataset and evaluates the comparison logic client-side providing a correct result set at the cost of performance.

Consider the example query below.

SELECT * FROM IssueFixVersions WHERE IssueId > '10005'

When KeyColumnOperators is set to "Server-Side", this is internally transformed into:

SELECT * FROM IssueFixVersions WHERE IssueCreatedDate > '2024-11-26T10:08:51Z'

Columns


Name	Type	References	SupportedOperators	Platform	Description
VersionId [KEY]	String		=,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN	Common	The unique identifier of the fix version assigned to the issue, used to track when and where a bug or feature was resolved.
IssueId [KEY]	Integer	Issues.Id	=,<>,>,>=,<,<=,IN,NOT IN	Common	The internal numeric ID of the issue that has been associated with this fix version.
IssueKey	String	Issues.Key	=,<>,>,>=,<,<=,IN,NOT IN	Common	The human-readable key of the issue, such as 'PROJ-123', which links it to the fix version.
IssueCreatedDate	Datetime		=,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN	Common	The timestamp indicating when the issue related to this fix version was originally created in Jira.
IssueUpdatedDate	Datetime		=,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN	Common	The timestamp indicating the most recent update made to the issue associated with this fix version.
Name	String			Common	The display name of the fix version, often reflecting a product release or milestone, such as 'v1.0' or 'Q2 Patch'.
Archived	Boolean			Common	If the value is 'true', the fix version has been archived, meaning it is hidden from standard version pickers and no longer actively used in projects.
Released	Boolean			Common	If the value is 'true', the fix version has been officially released, typically signifying that associated issues have been completed or deployed.
ReleaseDate	Datetime			Common	The scheduled or actual release date of the fix version, used for tracking project milestones and timelines.

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.