What is a historical record?
How history is stored in Targetprocess?
A Historical record is basically a copy of an entity with a time period definition.
For example, we have a User Story #123 'Shopping bag' was created on 01/01/2017 in the Project 'E-commerce' and is now in the 'In Testing' state. The structure of history for this User Story will look like this:
| ID | UserStoryID | Name | CreateDate | Project | Entity State | Date | DateTo | IsChangedName | IsChangedEntityState |
|---|---|---|---|---|---|---|---|---|---|
| 1 | 123 | Basket | 01/01/2017 | E-commerce | Open | 01/01/2017 13:46 | 02/01/2017 14:02 | False | False |
| 2 | 123 | Shopping bag | 01/01/2017 | E-commerce | Open | 02/01/2017 14:02 | 03/01/2017 09:18 | True | False |
| 3 | 123 | Shopping bag | 01/01/2017 | E-commerce | In Progress | 03/01/2017 09:18 | 04/01/2017 21:03 | False | True |
| 4 | 123 | Shopping bag | 01/01/2017 | E-commerce | In Testing | 04/01/2017 21:03 | 01/01/9999 23:59 | False | True |
As you can see, every record represents one or several changed fields.
All the updates made within 5 minutes are merged into one historical records. The only exception is EntityState: any change of EntityState will be represented as new History record.
The 'Date' and 'DateTo' fields represent periods in which the record is valid. If the record is valid right now, it has 'DateTo' set to the year 9999. At any given point in time, only one historical record is valid for any entity.
The 'UserStoryId' field is a reference to our User Story.
The 'IsChanged...' columns show which fields were changed compared to the previous record.
Here is how a Timeline-based graphical representation for our User Story would look like:
Custom Fields
It is possible to access historical values of Custom Fields via api/v2. More details here.
Limitations
Not all the fields are present in historical records.
Here are some of the examples of the missing fields with the link to the corresponding ideas in our Service Desk:
Updated over 2 years ago