Parent and Linked Entities
An entity in Targetprocess may have multiple parent and linked entities. Custom formulas support references to these entities and their properties. Access nested properties using dots.
EntityState.Name
Project.ID
Most common entity type is User Story. Here we'll describe how to refer to parent and linked entities in custom formula metrics used in custom fields at User Stories level.
Here is how to access basic properties of parent and linked entities at User Story level. Some of the formulas are valid for other entity types such as Bugs, Tasks, etc.
Entity Types | Custom Formulas | Result Types | Result |
|---|---|---|---|
User Story | Feature.Name | Text | Fields of parent Feature |
User Story | Feature.Epic.Name | Text | Fields of parent Epic |
Assignable Entities | Project.Name | Text | Fields of parent Project |
Assignable Entities | Project.Program.Name | Text | Fields of parent Program |
User Story | Release.Name | Text | Fields of parent Release |
User Story | Iteration.Name | Text | Fields of parent Sprint (Iteration) |
User Story | TeamIteration.Name | Text | Fields of parent Team Iteration |
Assignable Entities | LinkedTestPlan.Name | Text | Fields of linked Test Plan |
Use the formula below to inherit most commonly used values and properties from parent entities: Features and Epics.
Entity Types | Custom Formulas | Result Types | Result |
|---|---|---|---|
User Story | Feature.ID | Number | ID of parent Feature |
User Story | Feature.Name | Text | Name of parent Feature |
User Story | Feature.FieldName | Text* | Value of Text Custom Field named "Field Name" of parent Feature |
User Story | Feature.FieldName | Number* | Value of Numeric Custom Field named "Field Name" of parent Feature |
User Story | Feature.BusinessValue.Name | Text | Business Value of parent Feature |
User Story | Feature.BusinessValue.Importance | Number | Numeric importance of Business Value of parent Feature |
User Story | Feature.Epic.ID | Number | ID of parent Epic |
User Story | Feature.Epic.Name | Text | Name of parent Epic |
User Story | Feature.Release.ID | Number | ID of Release of parent Feature |
Access to custom field values is different for Metrics and Calculated Custom Fields
In formulas of Calculated Custom Fields to get value of Custom Field "Field Name" use:
FieldName
In formulas for Metrics to get value of Custom Field "Field Name" use:
CustomValues.Text("Field Name")
CustomValues.Number("Field Name")
CustomValues.Date("Field Name")
CustomValues.Boolean("Field Name")
Here is how you refer parent entities on different level of hierarchy: from Task to Program.
Any field and property of parent entities is supported
The examples below use .Name property as most frequently used one. Other fields, properties, collections are fully supported in the formulas as well.
Entity Types | Custom Formula | Result |
|---|---|---|
User Story | Feature.Name | Name of parent Feature |
User Story | Feature.Epic.Name | Name of parent Epic |
Task | UserStory.Name | Name of parent User Story |
Task | UserStory.Feature.Name | Name of parent Feature |
Task | UserStory.Feature.Epic.Name | Name of parent Epic |
Feature | Epic.Name | Name of parent Epic |
User Story | Project.Name | Name of parent Project |
User Story | Project.Program.Name | Name of parent Program |
Updated about 4 years ago