This feature is available in Enterprise and Ultimate editions.
The following table describes the columns available in the Fact.Effort table.
|EffortKey||Datamart unique identifier for this entry||int|
|Audit||VersionOne identifier for this entry||int|
|DateKey||Date this entry was reported as Foreign Key relationship||int||Dim.Date|
|Date||Date this entry was reported||datetime|
|MemberKey||Member reporting effort||int||Dim.Member|
|WorkitemKey||Identifies the Workitem where effort was reported||int|
|ProjectKey||Identifies the Project where effort was reported||int||Dim.Project|
|IterationKey||Identifies the Iteration where effort was reported||int||Dim.Iteration|
|TeamKey||Identifies the Team reporting effort||int||Dim.Team|
|PrimaryWorkitemKey||Identifies the Primary Workitem associated with this entry||int||Dim.PrimaryWorkitem|
|SecondaryWorkitemKey||Identifies the Task or Test associated with this entry||int||Dim.SecondaryWorkitem|
|ThemeKey||Identifies the Theme associated with this entry||int||Dim.Theme|
|EpicKey||Identifies the Epic associated with this entry||int||Dim.Epic|
Note: The term "historically accurate" means that the attributes are correct at the time the Effort is recorded and do not change. For example, if effort is recorded against a Defect in project X and that Defect is moved to project Y, the Effort record does not reflect the move. If you need Effort based on current attributes values, consider using the Done column in Fact.PrimaryWorkitem, Fact.Task, Fact.Test, or Fact.Workitem