We need to be able to support the following access and restrictions:
1. SCRUM Masters should be able to create versions. Developers and QA should not be able to create versions.
2. Anyone should be able to add a ticket to a version.
3. IS should be able to release versions. No one else should be able to release versions.
At a minimum we need to only allows users in a specific group (the Information Systems group) to release a version while allowing others to create versions. This does not seem to be possible with the built in permission system. Can it be accomplished by modifying a velocity template or some other means?
Hi
Version creation is a part of the 'administer projects' privileges in the Permission Scheme used by the project. Version creation is not a separate permission that you can set as of today.
Duplicate question of https://answers.atlassian.com/questions/14199
Hi Joe
If you explain your question, maybe someone able to help you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.