Data warehouse relationships missing?
I have a request from my users to update the out of the box RTC reports to prompt further down, so instead of just Program -> Project, add a 3rd layer so the report prompts for Program -> Project -> Category. This seems like a logical request, and definitely something we'll need to implement for our ClearQuest users also, but the data model and data warehouse definition don't seem to support the relationship between Projects and Categories.
I know the first answer is always "you can customize it", but I'm asking because I want to make sure I'm not missing a reason why you would I checked the RQM reports and they seem to do this sort of backwards. Instead of linking from Project to Test_Category, the reports look up from Project -> Testcase -> Category (for example) to determine the list of Categories. While this works, it then also only shows Categories that have been used. It seems just as valid of a use case to show that a Category has no related request records, rather than not give the Category as an option in the selection list. Does anyone have any thoughts/comments on this? |
2 answers
sorry about the inconvenience
it's in 2012 release plan now: 180283: RIODS.REQUEST_CATEGORY add column PROJECT_ID |
Thank you for the info! I feel much more comfortable making this update myself, knowing it is planned for a future release.
Also, is this tracked in a Jazz.net workitem that I can subscribe to and track the status? |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.