Is it possible to give permission to any user in the same group to change configuration for reports/graphs generation.
I have created a report and there is one field that changes in the filtering. My colleague wants to change that field and generate a report but he is not allowed.
(I already tried to set us both as admin)
The report is in the public folder and he can not change the filter settings (the filter icon is disabled).
I had already checked the group admin settings and they should allow it to my opinion (All boxes are set in the Dashboard tab including Standard Reports - Modify Public Reports).
It is not an excel-report but a requirements - requirements report or requirements - summary graph.
As a work around he copied the report and he is able to change the filter, but this will generate a lot of extra instances of the report (that are not needed) because multiple people use those reports to generate statistics.
Have you checked the permissions in Tools > Customize > Groups and Permissions. Select the group you belong to. Select the Permissions > Dashboard tab. Find the Graphs section and look at the Update option. It has a secondary check box for By Owner Only. If that is checked, then only the person who created the report can modify it. For the original, default groups supplied with the QC product the By Owner Only checkboxes are all unchecked, and you can't change them. But if you have created your own custom groups, then the checkbox may have been checked.
(Opinions and information contained in this post are wholly my own and do not reflect the opinions of my employer.)
The permission are set ok for 'TDAdmin' (even the extra checkbox "Owner Only")
Nevertheless this gave me an extra clue. Our users are part of multiple groups. The developer group has by default this switched on. I removed this group for that particular user and guess ... he is able to change it.
I am not sure if this would be a feature or a bug. Our particular case is that we defined one extra group based on 'TDAdmin' to limit the updates on the customer defined fields.
Maybe this interferes with the HP logic.
Trudy, thank you for the hint as our problem is solved.