Don't understand roles

Fré de Vries

In Jira/Greenhopper ( still don't know wich part of my installation is Greenhopper and wich is Jira) in the default installation there are three groups: users, developers and admins.

As we are using the Scrum method, as admin I created a Scrumboard.

We have a small team of 4 developers (1 of them is scrum master) and a project owner (me), I'm also the Jira-admin.

As a project owner, i create stories. I reorder them with drag&drop, the most important story on top.

I would like to give the scrum master more permissions, like drag&drop reordering, estimate , change status. But every developer has this permissions. Every developer can rearrange the order of the issues, change descriptions, summary, components etc. Why is this the case?

Why aren't there a project owner and scrum master roles by default?

Nic Brough -Adaptavist-

Because Greenhopper is an add-on for Jira and not a core function. A LOT of Jira installs don't have it, and some aren't used for Agile at all. It's added complexity for users who don't need it, and the default installation of Jira is very basic. Jira is powerful and flexible, but that makes administration complex, and it's already scary enough without adding roles some sites may not need or understand.

There is already a "project owner" role as well. It's called "project lead" and is associated with the projects (even without Greenhopper). I think the simple assumption is that "project lead == scrum master == project owner" and the defaults do that, and then expect users to create the more compex situations as they discover the need for them.

That said, I think there's a request open for improved defaults, and I'd support it. (My main bugbear is that "jira users = can login" but is then used to do other things in permissions, and that's a stupid default for any site that wants to do any form of sane security)