permission to attach files to work items at wrong level?
We try to limit user permissions only to the teams they belong to.
Permissions to perform some of the activities have to be set at the "project level". This is fair enough and only very select few will have Scrum Master privilege at project level. But why is permission to attach files to work items set at project level? This means we have to add all users as project members. Making team structure, to a certain extent, meaningless (as well as double the amount of work). There can also be process and procedural issues with this. Permissions to manipulate attachments should be set at team level and not project level. |
One answer
Ralph Schoon (63.5k●3●36●46)
| answered Jul 16 '13, 1:25 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Please consider reading https://jazz.net/library/article/291 and https://jazz.net/library/article/292 because there is some inheritance involved that determines what role you have in which context.
Comments I understand the inheritance. My point is that I do not want to assign roles to users at any higher up in the hierarchy than necessary.
|
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.
Comments
Oops forgot to mention the "fair enough" activies are to do with timeline and iteration manipulations.