Bridge Tables
This topic explains the usage of bridge tables for multi relationships in Agility.
Overview
Bridge tables are used to when a multi-multi relationship exists. An example of such a relationship is the Task Owner field. In Digital.ai Agility Task can be owned by several owners (Members) and any one Member can own several Task. In the VersionOne datamart, all Bridge tables are in a database namespace (schema) known as "Bridge". The following bridge tables are available for slicing facts and dimensions
- Epic Owner
- Epic Strategic Theme Assignment
- Member Groups
- Primary Workitem related to Request
- Project Member
- Project Program
- Story Dependency
- Tags
- Workitem Owners
- Workitem Broken By Defect
Bridge tables to help with Build Run Reporting
- Defects Found In Build Runs
- PrimaryWorkitem Completed In BuildRun
Bridge tables to help with Goal Reporting
- Goals Targeted By Project
- Primary Workitem related to Goals
Bridge tables to help with Issue Reporting
- Blocking Issues on Primary Workitems
- Blocking Issues on Epics
- Issues Resolved