Security permissions of RQM custom reports vs Project Areas
Hi,
I have to create different RQM project areas to store test assets because due to security restrictions users of some projects can not see information from other projects. For example, user A can view and modify only test info from Project Area A and user B can view and modify test info from Project B. RQM allows to manage this structure using different different project areas without problems. But problems come when using custom reporting included in RQM. I design a template for listing test cases, but as security in custom reporting is not the same the user A can list test cases of Project A and B. Only possibility would be to create different reports for Project A and B and filter in the report the project area to access to, but for a customer with 20 project areas this is not usable. The reports that come by default in RQM 2.0.0.1 already implement these security mechanisms and users can only see info from their project areas, but How have been these reports built? Using BIRT? Or using the RQM custom reporting? Because if I import custom reporting Test Case -> Test Cases does not work (it shows all project areas info) but if I use just standard deployed report (without using custom reporting) this works and user has only access to info of his project area. Is BIRT already officially supported as a reporting mechanism in RQM? Thanks, Ana |
2 answers
Hi Ana,
You are correct, the reports built into RQM are BIRT based reports and are restricted to report against the "current" project area. Mark |
On 12/6/2009 2:52 AM, MVictory wrote:
You are correct, the reports built into RQM are BIRT based reports and security controls for project areas visibility if reports are built with RQM custom reporting (i.e Insight)? |
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.