Skip to main content

Bridge Tables

Bridge tables are used when a multi-multi relationship exists. An example of such a relationship is the Task Owner field. In Digital.ai Agility, a Task can be owned by several owners (Members) and any one Member can own several Tasks. In the VersionOne datamart, all Bridge tables are in a database namespace (schema) known as "Bridge".

Multi-Multi Relationship Bridge Tables​

Bridge.EpicOwner​

Members can own multiple Epics and any Epic can be owned by multiple members. This relationship changes over time.

Table Description​

Column NameDescriptionDatatypeForeign Key To
DateKeyIdentifies the date this record is validintDim.Date
EpicKeyIdentifies the Epic owned by a memberintDim.Epic
MemberKeyIdentifies the Member owning the EpicintDim.Member

Bridge.EpicStrategicTheme​

Portfolio Item (Epics) can be related to multiple Strategic Themes.

Table Description​

Column NameDescriptionDatatypeForeign Key To
EpicKeyIdentifies the EpicintDim.Epic
StrategicThemeKeyIdentifies a Strategic Theme associated with the EpicintDim.StrategicTheme

Bridge.MemberGroup​

Members can be a part of many Member Groups.

Table Description​

Column NameDescriptionData TypeForeign Key To
MemberKeyIdentifies the Member in a Member GroupintDim.Member
MemberGroupKeyIdentifies the Member GroupintDim.MemberGroup

Bridge.PrimaryWorkitemRequest​

Stories and Defects (PrimaryWorkitems) can be related to many Request.

Table Description​

Column NameDescriptionDatatypeForeign Key To
PrimaryWorkitemKeyIdentifies the Primary WorkitemintDim.PrimaryWorkitem
RequestKeyIdentifies the RequestintDim.Request

Bridge.ProjectMember​

Members are allowed to view many projects.

Table Description​

Column NameDescriptionDatatypeForeign Key To
MemberKeyIdentifies the Member that can observe this projectintDim.Member
ProjectKeyIdentifies this projectintDim.Project

Bridge.ProjectProgram​

Programs contain many projects.

Table Description​

Column NameDescriptionDatatypeForeign Key To
ProjectKeyIdentifies the Project assigned to the ProgramintDim.Project
ProgramKeyIdentifies the programintDim.Program

Bridge.StoryDependsOnStory​

Stories can depend on other Stories. As of the Fall 2014 release (14.3.x), this table has been deprecated and will be removed from a future release of the product. To create reports on dependencies, use the Bridge.PrimaryWorkitemDependencies table.

Table Description​

Column NameDescriptionDatatypeForeign Key To
UpstreamStoryKeyIdentifies the Story that must be completed first in a dependency relationshipintDim.PrimaryWorkitem
DownstreamStoryKeyIdentifies the Story that is waiting for something else to completeintDim.PrimaryWorkitem

Bridge.PrimaryWorkitemDependencies​

This table contains 1 row for each Primary Workitem Dependencies defined in your core instance. This table was not available before the Fall 2014 release (14.3.x). For reporting on dependencies in Summer 2014 (14.2.x) and prior, you will need to use the Bridge.StoryDependsOnStory table.

Table Description​

Column NameDescriptionDatatypeForeign Key To
UpstreamPrimaryWorkitemKeyIdentifies the Primary Workitem that must be completed first in a dependency relationshipintDim.PrimaryWorkitem
DownstreamPrimaryWorkitemKeyIdentifies the Primary Workitem that is waiting for something else to completeintDim.PrimaryWorkitem

Bridge.Tags​

Tagging is a lightweight, flexible way for different groups to organize data according to their needs. To create reports on Tags, or to use Tags in filters, use the Bridge.Tags table.

Table Description​

Column NameDescriptionDatatype
AssetKeyIdentifies the Tagged Asset.int
ValueIdentifies the tag valuenvarchar(1000)

Technical Details​

This table contain 1 row for each tag-able asset and each tag. Therefore, if a Story contains 3 tags, there are 3 rows in this table for that story, each row has one of the tag values.

This table is not historical. The Data Mart does not support reporting on historical tag values.

Tag List Views​

Views exist to consolidate tag values to their asset. This can make reporting on Tags easier. The views are:

  • Dim.EpicTagListView
  • Dim.IssueTagListView
  • Dim.PrimaryWorkitemTagListView
  • Dim.RegressionTestTagListView
  • Dim.RequestTagListView
  • Dim.SecondaryWorkitemTagListView

Bridge.WorkitemOwner​

Members can own multiple workitems and any workitem can be owned by multiple members. This relationship changes over time.

Table Description​

Column NameDescriptionDatatypeForeign Key To
DateKeyIdentifies the date this record is validintDim.Date
WorkitemKeyIdentifies the workitem owned by a memberint-
MemberKeyIdentifies the Member owning the workitemintDim.Member

Bridge.PrimaryWorkitemBrokenByDefect​

This table contains 1 row for each Primary Workitem broken by a Defect in your core instance. This table was not available before the Fall 2015 release (15.3.x).

Table Description​

Column NameDescriptionDatatypeForeign Key To
PrimaryWorkitemKeyIdentifies the Primary Workitem that is BrokenintDim.PrimaryWorkitem
DefectKeyThe Defect breaking the associated Primary WorkitemintDim.PrimaryWorkitem

Build Run Reporting Bridge Tables​

Bridge.DefectFoundInBuildRun​

When Defects are reported, the user can select which build contained the defect.

Table Description​

Column NameDescriptionData TypeForeign Key to
DefectKeyIdentifies the DefectintDim.PrimaryWorkitem
BuildRunKeyIdentifies the BuildRunintFact.BuildRun

Bridge.PrimaryWorkitemCompletedInBuildRun​

When a PrimaryWorkitem is closed, the last associated BuildRun is the run where it was determined complete.

Table Description​

Column NameDescriptionDatatypeForeign Key To
PrimaryWorkitemKeyIdentifies the Primary WorkitemintDim.PrimaryWorkitem
DownstreamStoryKeyIdentifies the Build RunintFact.BuildRun

Goal Reporting Bridge Tables​

Bridge.GoalTargetedByProject​

When a Goal is targeting a project, the project has work that helps the organization achieve the goal.

Table Description​

Column NameDescriptionDatatypeForeign Key To
GoalKeyIdentifies the GoalintDim.Goal
ProjectKeyIdentifies this projectintDim.Project

Bridge.PrimaryWorkitemGoal​

Primary Workitems can be related to many Goals and this relationship may change over time.

Table Description​

Column NameDescriptionDatatypeForeign Key To
DateKeyDate this record is validintDim.Date
PrimaryWorkitemKeyIdentifies the Primary Workitem assigned to the GoalintDim.PrimaryWorkitem
GoalKeyIdentifies the GoalintDim.Goal

Issue Reporting Bridge Tables​

Bridge.PrimaryWorkitemBlockedByIssue​

Issues can block PrimaryWorkitems. This relationship changes over time.

Table Description​

Column NameDescriptionDatatypeForeign Key To
DateKeyIdentifies the date this record is validintDim.Date
PrimaryWorkitemKeyIdentifies the blocked PrimaryWorkitemintDim.PrimaryWorkitem
IssueKeyIdentifies the IssueintDim.Issue

Bridge.EpicBlockedByIssue​

Issues can block Epics. This relationship changes over time.

Table Description​

Column NameDescriptionDatatypeForeign Key To
DateKeyIdentifies the date this record is validintDim.Date
EpicKeyIdentifies the blocked EpicintDim.Epic
IssueKeyIdentifies the IssueintDim.Issue

Bridge.PrimaryWorkitemResolvedIssue​

PrimaryWorkitems can be created and used to resolved Issues.

Table Description​

Column NameDescriptionDatatypeForeign Key To
PrimaryWorkitemKeyIdentifies the blocked PrimaryWorkitemintDim.PrimaryWorkitem
IssueKeyIdentifies the IssueintDim.Issue