Most organizations have special needs for reporting on their projects. While V1 has some reporting capabilities, and it could add more, it's difficult to anticipate all the possible reporting needs. There are many reporting tools available that could be used if the data in the database were more easily understandable.
Denormalized, read-only views on the data would go a very long way with making the data more accessible to reporting tools.
For example, make a view called "Stories" that would contain one row per story with information "rolled up"; that is it would include all attributes in lower-level included objects like PrimaryWorkItems, WorkItems, etc. all the way to BaseAsset. Would also include counts of children tasks/tests, IDs of parents and related items, etc. With that a reporting tool could easily access the information.
Note: I'm not knocking at all the database design - I understand the why it is the way it is and it makes good sense. But it is difficult to understand without a lot of study.
by: Greg Y. | over a year ago | Reporting & Analytics
Comments
This one can be closed now as it is the same as the Custom Reporting idea that has already been implemented.