I'm just starting to look at JIRA and here are some thoughts:
I can identify the following roles:
- user
- developer (contributor but not committer)
- committer
- admin
I browsed the JIRA docs and I'm still looking for a workflow diagram to
better understand the lifecycle of a JIRA issue, but here's what I think
each of these roles will want to do:
- As a user I want to be able to report and modify issues, resolve
(cancel?) and close/verify issues that I've opened.
- As a developer I want to be able to do all of the above, plus assign
issues that have not been assigned yet, modify issues, resolve issues
assigned to me (duplicate or not repro for example?) and attach patches
to them (assuming that this is how patches get contributed).
- As a committer, I want to be able to do all of the above plus resolve
issues (as fixed for example after checking in) and reassign issues.
- As an admin I want permission to do everything.
What do people in the group think? Jeremy, does that fit with the JIRA
user-type / permission model?
--
Jean-Sebastien Delfino
Jeremy Boynes wrote:
The default JIRA permission setup has a few different types of users:
* "anyone", basically anonymous, who can view things
* "jira-user", people who have accounts, who can create issues
and add information to them
* "tuscany-developers" who can modify issues, assign them, close them
for the Tuscany project (e.g. a committer)
* "jira-admins" who can configure JIRA itself and modify things about
projects
This generally works well but raises a question for people who are
actively involved in the project but who are not yet committers: what is
the policy for allowing them to modify issues?
A few options we have here are:
* restrict it to committers and have them update the issues as needed
* be fairly liberal about granting "developer" status to contributors
* create a custom permission level somewhere between "user" and
"developer" and grant that to contributors
Any thoughts, suggestions and/or preferences?
--
Jeremy
