I'm setting up permissions on a project, and I'd like to be able to give the "Browse Projects" permission to any user who has an assigned role on that project. I could specify each role, but if I then created a new role at a later date, I'd need to ensure that I'd edited the permissions to add it. Whereas having "any assigned user" means that any user linked to that project would immediately have access to that permission.
No, assigning the roles is the only way. I have a role 'project user' that I give most of the permissions to including browse, create, edit, add attachments, etc. Everyone working on the project gets that role. The 'special roles' like tester, developer, QA, and such are used as conditions for workflow transitions.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...attest to the experience of an urgent approval that gets lost in the boss’s inbox and requires that special “Please Approve” email or text message. In an age where we have distributed teams...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs