RELATED IDEAS
Support deeper joins than second level on the dependency report
The Problem
Currently it is only possible to add data from one level deep on the dependency report. So for example, you can add master feature name when features are your dependent record type. But you cannot add the master features' release name.
The related tables should be available at each level on the dependent record side.
Thanks for supporting second level data for the dependent records. However, we would like to see release information of features in the primary column. For example, if the release of the feature in the primary column was changed and now the feature is being release after dependent feature, there is no way for us to identify this problem from the report.
Will this be supported in the future?