Hello! So, you'd think this isn't a complicated issue but... Our program managers don't want everyone working on a specific project to be able to move issues around. They'd like them to only be able to move the issues they've created so that other folks items aren't accidentally moved. I have created a permission scheme that allows the ONLY administrators for that particular project to move issues. When we tested it out, someone that wasn't in the administrator group was still able move everything around. Did I do something incorrectly in setting up the permission scheme? Or is there another route I should take to make this happen? Thanks in advance!
When you say "moved around", do you mean "move issues" (between issue types and/or projects), or do you mean transitions through the workflow? Or something else?
The program manager would like for his team not to be able to move issues off the backlog into sprints or move them around. They are trying to put their backlog issues in order or priority based on customer preference.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Users with the Schedule Issue and Edit Issues permissions can move issues in and out of sprints and up and down the backlog.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Exactly where I was headed, thanks @Robert Barrow
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! Is there a way that they can only move the issues they created up and down the backlog/into sprints? Or is it all or nothing?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, only grant them schedule and edit. Do not grant them "transition"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, I want them to be able to transition their work through the workflow... We just don't want them to be able to move other user's issues up and down the backlog. It doesn't seem like this is possible though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess you could introduce a Issue Security scheme, but that would mean that they can only see their own tickets, which might not be what you're after.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
>So, I want them to be able to transition their work through the workflow
Ok, that's the exact opposite of what you asked before, but it is also possible - If you want them to transition but not move them up and down the backlog, then do NOT give them schedule and edit, but do grant them transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey Tiffany,
Check the Project Permissions and Users and Roles section to see who is included in the "Move Issues" permission and who may be a project admin.
Hope this helps,
Tyler
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tyler, I created Project Permissions and separate user roles for this particular instance. I selected just the administrators for the "Move Issues" section, but it appears other issues can still move issues around.
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.