If I'm creating a project where the different transitions would need to be controlled by different project specific roles (not groups), how do I go about it?
In essence, I'm wondering if it's possible at the Role level or better yet at the permission schema level to only allow "people in the validators Role" to press the "Assign" button or only "people in the developer role" to press the "in progress" button etc.)
It's even more flexible than that. Have a look at the "conditions" on the workflow transitions and you'll see two broad types - direct and indirect. Direct ones say things like "only people in role X can do this". Indirect ones say things like "only people with permission Y can do this" - they go through the permission schemes.
In fact, you're generally discouraged from using groups in conditions at all, roles are the better way to do it. Have a look at the built in workflows to see how they do it.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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