Within the Plan section of Greenhopper, it is possible for people other than the Product Owner to change the order of the backlog, and even worse - add items to a current sprint.
In my mind this is incorrect as the PO owns the backlog and what is commited to a sprint, therefore nobody else should be able to do this.
I can't find any way of restricting the re-ordering of the backlog (or adding items into a sprint) - surely there is a way to do this? Anybody able to point me in the right direction?
I am using JIRA 6.0.1 and Greenhopper 6.2.2 - I am not using the Classic boards.
As of now, the right to rank Issues is derived from the Schedule Issues Project Permission, so you may want to make sure that only the PO has it. As for adding and removing Issues from Sprints, that's based on the Edit Issues Permission - so limiting this would affect more users. You may want to vote for this related feature request, though: GHS-7881.
See this article for details on how GreenHopper inherits Permissions from JIRA: GreenHopper JIRA Configuration - Permissions.
Ok, just removed the schedule permission from the developers group, and indeed they can now not reorder the backlog or move an item into a sprint
They can not not edit any of the issues. i need them to be able edit the issues, just not move them within the backlog. =(
I re-enabled the schedule permission and the user can now edit issues (although they can obvioulsy schedule them as well now).
I had already created a new user in our test instance to check everything out.
There are no limitations on the workflow except when moving between a done and closed status.
The developer group should be able to edit issues. With the schedule permission revoked, the group can't edit issues is not workable, that's even worse than the orginal problem.
I would say the PO owns the backlog and the development team owns the sprint backlog. Also, I would think that the development team "commits" to what it can accomplish, but you would want them to be able to pull issues into a sprint from the backlog (ordered by the PO) if time permits.
Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the 104 years logged in 2017 , and we aren’t even through December yet....
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