IssueLinks

Displays relationships between issues, such as 'blocks', 'duplicates', or 'relates to'.

Table Specific Information

You can search IssueLinks 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 IssueLinks are IssueId, IssueKey, and JQL. For example:

SELECT * FROM IssueLinks 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 IssueLinks WHERE IssueId > '10005'

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

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

Columns


Name	Type	References	SupportedOperators	Platform	Description
Id [KEY]	String			Common	The unique identifier of the issue link, representing a specific relationship between two issues in Jira.
InwardIssueId	Integer	Issues.Id		Common	The numeric ID of the issue that is linked to the current issue, acting as the inward target in the relationship.
InwardIssueKey	String	Issues.Key		Common	The key of the issue that is linked to the current issue, such as 'BUG-102' or 'TASK-301'.
OutWardIssueId	Integer	Issues.Id		Common	The numeric ID of the issue that the current issue is linking to, acting as the outward reference in the relationship.
OutwardIssueKey	String	Issues.Key		Common	The key of the issue that the current issue is linking to, such as 'EPIC-501' or 'STORY-210'.
IssueId [KEY]	Integer	Issues.Id	=,<>,>,>=,<,<=,IN,NOT IN	Common	The numeric ID of the issue that owns or originates this link.
IssueKey	String	Issues.Key	=,<>,>,>=,<,<=,IN,NOT IN	Common	The key of the issue that owns or originates this link, such as 'PROJ-123'.
IssueCreatedDate	Datetime		=,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN	Common	The date and time when the originating issue for this link was created in Jira.
IssueUpdatedDate	Datetime		=,<>,>,>=,<,<=,IS,IS NOT,IN,NOT IN	Common	The date and time of the most recent update made to the originating issue associated with this link.
TypeId	Id			Common	The identifier of the type of relationship, such as 'blocks', 'relates to', or 'duplicates'.
TypeName	String			Common	The descriptive name of the issue link type, such as 'is blocked by', 'relates to', or 'duplicates'.

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.