How can i revoke users in the Developer group adding issues to a sprint from a backlog without removing the edit issue permission?
Removing the Schedule Issues permission still allows issues to be added to the sprint.
I only want either the Project Lead/Admin Group to be the only users to action this.
I would have thought this would be standard setting?
Thanks for your OPINION,
I'm well aware of the schedule and edit permission behaviour, hence why i raised a question to see if there were alternatives as previous support questions have always provided professional answers or alternatives. I may rethink this now.
In my CONTEXT, agile projects and sprints are managed by a Project/Product owner, priorities are not dictated by a developer. If a sprint is in progress it would suggest that the Project/Product owner has set a number of issues for the sprint based on estimates to accurately use the tool to it full extent i.e. burndown chart utilistations, sprint retrospectives... again one of the points for making Greenhopper a great tool along with other Atlassian products.
Just had to comment on this. I find it interesting that their documentation says otherwise.
https://confluence.atlassian.com/display/AGILE/What+are+the+permissions+used+in+Agile+Boards
Only users with Project Administrator permissions (as per Project Permissions) can add/drag issues into sprints.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Simply put, you can't. The ability to add an issue to a sprint is tied to the Edit Issue permission. The Schedule issues permission is only relevant when ranking an issue, e.g. you are moving an issue into the sprint, AND ranking at the same time.
If you simply right click on the issue in the backlog and select "SEND TO ... Sprint XX" then its just the edit issue permission that is required.
Well, in my opinion, developers SHOULD be able to add issues to sprints, since they are going to be working on them. (Which would in turn need the Edit Issue permission to actually WORK on an issue)
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.