Custom Fields
An entity in Targetprocess may have multiple custom fields - up to 100 actually. Here we'll describe how to refer to custom field values in formulas used for Custom Formula Metrics and Calculated Custom Fields.
Inherit Custom Field values from an entity itself
Custom Formula Metrics:
Custom fields have various types. Custom formula metrics can extract values from fields of the following types:
- Text
- Number
- Date
- Boolean
- Entity
Type of an extracted value is determined automatically. There is no need to specify it manually. You just use name of the field. If a field name has spaces, skip them in your formulas.
| Resource | Meta information | Endpoints |
|---|---|---|
| Task | link |
/api/v1/TaskHistories /api/v2/TaskHistories /api/history/v2/Task |
| Bug | link |
/api/v1/BugHistories /api/v2/BugHistories /api/history/v2/Bug |
| User Story | link |
/api/v1/UserStoryHistories /api/v2/UserStoryHistories /api/history/v2//UserStory |
| Feature | link |
/api/v1/FeatureHistories /api/v2/FeatureHistories /api/history/v2/Feature |
Inherit Custom Field values from parent entity
Besides references to fields at own level entities can inherit custom field values from parent entities. Say a User Story, which is a most common entity type in Targetprocess, can inherit custom field values from parent entities: Features, Epics, Projects, etc. Same formulas are valid for other entity types such as Bugs, Tasks.
| Resource | Meta information | Endpoints |
|---|---|---|
| Task | link |
/api/v1/TaskHistories /api/v2/TaskHistories /api/history/v2/Task |
| Bug | link |
/api/v1/BugHistories /api/v2/BugHistories /api/history/v2/Bug |
| User Story | link |
/api/v1/UserStoryHistories /api/v2/UserStoryHistories /api/history/v2//UserStory |
| Feature | link |
/api/v1/FeatureHistories /api/v2/FeatureHistories /api/history/v2/Feature |