- Brief Description
Having the ability to produce a Trace Matrix or "Relationship Matrix" Reporting feature within an Octane Workspace would be ideal without having to utilize a OData connection or some other outside method. Having the ability to do this report within a Dashboard widget or similar process would allow users to report on overall relationship coverage, have it be Epic to Feature, or the entire relationship such as Epic, Feature, User Story, Acceptance Criteria, Test Case, Defect (if found).
- Benefits / Value
As the adoption of any new tool takes time, having the ability to provide reports, graphs, flows against your data set is always a good thing for Management and ultimately the end users who are the ones adopting the new tool and or processes. Showing the User base that Octane can report out in a logical way (perhaps like a parent\child\sibling flow) a Trace Matrix that allows you to see overall coverage relationships would be beneficial all the way through the process to insure proper coverage is being applied where needed. NOT having to utilize third party software, or outside data extraction tools to crunch and report the Trace relationships would be best from a single point of interface perspective as well as a managed system aspect.
- Design details
I see this Trace "Relationships" Matrix functionality be best served as a non-Excel based report, perhaps like the way the Relationship tree looks like currently, but just cleaner and more organized for reporting reason. I could see a Widget that does not actually create a visual graph for you, but allows you to Export a file that contains a graphic representation of all the Relationships you configured the widget for. The configuration could include a Graph Type = Relationship Matrix, and a major Scope setting would include the range of what you want to Trace to & from, such as Epic's thru to Test Cases. If there was a way (open source code engine) to export the Relationship Mapping into Visio, static JPG\PNG\etc. or some other respective file type that would be ideal.
The bottom is to just have a mechanism within Octane itself that allows a user to report on Trace\Relationships, and allow that same report to be exported. Obviously this report should be generated and presented to the user in a way conducive to its intentions, mainly graphic, but if it was to be exported into Excel, then it would need to have a visual layout that easily shows a "Parent" row and then all the associate "child" rows under that, and etc.
This report would only need to pull and report on the same data points as the current relationship view shows, Record Type, Record ID#, Record Name\Title, Record Status.