RQM v3.0.1 roles/permission changes
Since we migrated to v3.0.1 from v2.0.1.1 iFix 3, I've noticed some of the roles/permissions we had have changed (at least that is my perception).
Specifically, we created a Process->Save Project Area->Modify the collection of Team Members This is defined at the Project level. Now the testleads are not able to manage their teams through the test plan->test team->manage team button. Could this be related to a migration failure I'm unaware of? (The migration was done by the IT team and not me.) On a related note, I do not want the permissions to be set below the project level (ie. team or iteration level). Too many levels to remember which one has which access. What is the best way to ensure the project level is the only level of permissions being recognized? Do I need to select the "Final" check box for each area? rns |
One answer
A follow-up and new question:
- The project level permissions are the only ones that are in effect - Be sure to check your EVERYONE settings (that was my biggest problem) I'm still not quite understanding the new permission Is this true? I thought "archive" meant "delete" - which is something I want to restrict. Could someone confirm? rns |
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.