Help Contents
-
System Administration
-
User Guide & Application Administration Guide
-
Using Enterprise Tester
-
Application Administration
-
Searching & TQL
-
Simple Search
-
Advanced Search
-
Testing Query Language (TQL)
-
Aggregation
-
Fields
-
Accumulated Actual Duration
-
Actual Duration
-
Affected Version
-
Agile Runs Count
-
All Packages
-
AllParents
-
Assigned To
-
Assignee
-
Assignment
-
Assignment Id
-
Assignments Count
-
Attachment Count
-
Automated Tests Count
-
Blocked
-
Change Comment
-
Comment
-
Component
-
Created At
-
Created By
-
Description
-
Destination
-
Difficulty
-
Difficulty Level
-
Directly Related To
-
Editor
-
Editors
-
Entity Type
-
Errors
-
Estimated Duration
-
Estimated Less Actual Duration
-
Execution Totals
-
ExternalId
-
ExternalKey
-
ExternalUrl
-
Failed
-
Fields / Organisation
-
Fields / Package
-
Fields / Project
-
Fields / Relationship
-
Fields / Script
-
Finished At
-
Fixed Version
-
Has Agile Runs
-
Has Assignments
-
Has Attachments
-
Has Automated Tests
-
Has Coverage
-
Has Incidents
-
Has Requirements
-
Has Scripts
-
Id
-
Imported At
-
Incident Count
-
In Progress
-
Iterations
-
Key
-
Last Comment
-
Last Synchronized At
-
Last Updated At
-
Last Updated By
-
Name
-
Notes
-
NotRun
-
Number
-
Objective
-
Order Number
-
Organisation
-
Package
-
Parent
-
Parent And This Package
-
Parent Package
-
Passed
-
Post Condition
-
Pre Condition
-
Priority
-
Project
-
Provides Coverage
-
Query
-
Raised By
-
Related To
-
Related To All Packages
-
Related To All Parents
-
Related To Entity Type
-
Related To Fields
-
Related To Id
-
Related To Organisation
-
Related To Package
-
Related To Parent
-
Related To Priority
-
Related To Project
-
Related To Status
-
Related To Type
-
Relationship
-
Relationship Depth
-
Relationship Direction
-
Relationship Id
-
Relationships
-
Relationship Type
-
RelationshipTypeKey
-
Relationship Type Key
-
Remaining Estimate
-
Requirements Count
-
Resolution
-
Run By
-
Run Number
-
Script
-
Script Id
-
Script Priority
-
Script Status
-
Script Step Count
-
Script Type
-
Skipped
-
Source
-
Started At
-
Status
-
Step Actual Results
-
Step Data
-
Step Description
-
Step Expected Result
-
Step Notes
-
Summary
-
Test
-
Test Assigned To
-
Test Id
-
Test Scripts Count
-
Text
-
Ticket Id
-
Ticket Key
-
Ticket Url
-
Total Nodes
-
Total Results
-
Tracker
-
Type
-
Undetermined
-
Version Number
-
Version Of Script
-
Warnings
-
Accumulated Actual Duration
-
Functions
-
Indexes
-
Operators
-
Order By
-
SET
-
TQL For JQL Users
-
Types
-
Values
-
Aggregation
-
Simple Search
-
API
-
Using Enterprise Tester
-
Platform Plugins
-
Troubleshooting
-
Earlier Versions of this Documentation
-
Support & Bug Fixes
-
NextGen
Field: Relationships
Description
Relationships allows filtering entities based on their relationships to other entities, relationships can be direct, for example:
- Scripts that provide coverage for requirements.
- Assignments in an execution package which are associated to their script.
- The bugs related/raised during the run of a script assignment.
They can also be indirect, such as:
- Parent requirements of requirements that are related to scripts.
- Bugs related to a script or a requirement, via their associated script assignments.
Querying of the relationships index is done via a sub-select, and takes the basic form of:
Relationships IN { ... relationships sub-select query ... }
The query within the sub-select is executed against the Relationships Index and has access to all the Relationships index fields.
When searching the relationships index, you are effectively searching a list of all the relationships each entity has to other entities, both direct and indirect, so you compose your sub-select query in terms of the "Source" and "Destination" entities, the Destination entites expose a number of fields that start with "RelatedTo" which make it possible to identify the related entities.
Two convenience fields are also provided to simplifying searching for related entities RelatedTo and DirectlyRelatedTo which we recommend users become familiar with before branching out into learning how to use the Relationships index and it's fields.
Examples
All scripts related to requirements in the project 'Project X':
EntityType = Script AND Relationships IN { RelatedToProject = 'Project X' AND RelatedToEntityType = Requirement }
All indirectly related requirements for scripts in 'Cycle 1':
EntityType = Requirement AND Relationships IN { RelatedToPackage = 'Cycle 1' AND RelatedToProject = 'Project X' AND RelatedToEntityType = Script AND RelationshipDepth > 1 }
All requirements related to bugs with a resolution of "Wont Fix" raised in the last week (demonstrates the use of the Destination field and a nested sub-select back into the Entities Index):
EntityType = Requirement AND Relationships IN { Destination IN { Type = Bug AND Resolution = 'Wont Fix' AND CreatedAt >= "-1 week" } }
See Also
Supported Operators
Supported Indexes
Supported Types
- AgileRun
- AutomatedTest
- AutomatedTestAssignment
- AutomatedTestRun
- Incident
- Requirement
- RequirementPackage
- ScriptRun
- TestExecutionPackage
- TestScript
- TestScriptAssignment
- TestScriptPackage
Supported Features
Feature | Supported? |
---|---|
Aggregation | No |
Sortable | No |
Sub-selects | Yes |