Help Contents

 

Relationship Direction

Field: RelationshipDirection

Description

The relationship direction specifies the direction of the relationship, when searching the relationships index.

The relationship direction relates to the "Direction" column of the relationships tab, which is available on most edit screens:

Direction Values

TQL currently supports 4 directions (None, Both, Source -> Destination, Destination -> Source).

The text "Destination -> Source" is a bit tedious/error prone to write out in a query, so we also support a number of aliases for each value, to suite the tastes of different users, and to allow for values that can be used in some cases without quotes.

ValueAlias
DestinationToSourceDestinationToSource
DestinationToSource<-
DestinationToSource<=
DestinationToSource<
DestinationToSourceDestToSrc
DestinationToSourceDestination -> Source
DestinationToSourceSource <- Destination
SourceToDestinationSourceToDestination
SourceToDestination->
SourceToDestination=>
SourceToDestination>
SourceToDestinationSrcToDest
SourceToDestinationSource -> Destination
SourceToDestinationDestination <- Source
BothBoth
Both<->
Both<=>
Both<>
BothBiDirectional
BothBiDirect
BothBi Directional
BothBi-Directional
NoneNone
NoneNull
NoneEmpty
NoneUndefined

Examples

Get all requirements that are related to requirements that have a status of "Approved" and the direction of the relationship is bi-directional (association):

EntityType = Requirement
  And Relationships IN {
      RelatedToEntityType = Requirement
      AND RelationshipDirection = '<->'
      AND RelatedToStatus = Approved  
  }

Supported Operators

=, IN, !=, NOT IN

Supported Indexes

Relationship

Supported Types

  • AgileRun
  • AutomatedTest
  • AutomatedTestAssignment
  • Incident
  • Requirement
  • RequirementPackage
  • TestExecutionPackage
  • TestScript
  • TestScriptAssignment
  • TestScriptPackage

Supported Features

FeatureSupported?
AggregationYes (String)
SortableYes
Sub-selectsNo