Bug #485


Issue permissions are quirky

Added by Matt Lewandowsky over 12 years ago. Updated over 4 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Developers should have (mostly) a superset of issue tracker features of those of reporters. Likewise with reporters -> non-members -> anonymous.

Related issues

Related to site - Bug #206: Need better bug tracking systemRejectedSergey Generalov2010-09-15

Related to site - Feature #442: New Issue should be "available" to unauthenticated usersClosedSergey Generalov2010-12-05

Blocks site - Bug #165: redmine needs to lose its authoritarian streakIn ProgressSergey Generalov2010-09-07

Blocked by site - Bug #482: Reporters should be able to define bug dataResolvedMatt Lewandowsky2010-12-08

Actions #1

Updated by Matt Lewandowsky over 12 years ago

The following changes to the permissions have been made so far:

Anonymous (not logged in?):
  • No Changes at this time (see #442)
Non-member (logged in but not part of project?):
  • No Changes
  • May want to add Manage issue relations and/or Move issues at some future date
Reporter (has project's Reporter role):
  1. Added Manage issue categories
  2. Added Manage issue relations
  • May want to add Move issues at some future date
Developer (has project's Developer role):
  1. Added Move issues
  2. Added Edit own notes
Actions #2

Updated by Matt Lewandowsky over 12 years ago

  • Assignee changed from Matt Lewandowsky to Garrett D'Amore

I did the sane things for Reporters and Developers. At this point, we should discuss "non-members" in the context of the thoughts raised in #165 and "anonymous" in the context of both #165 and #442.

It wouldn't hurt reviewing to see if perhaps other permissions should be added, such as allowing reporters to move issues. However, I think things like that should be revisited when people mention them.

Actions #3

Updated by Garrett D'Amore over 12 years ago

Generally, we need to have a bug-tracking committee that can discuss the workflow here. I'd be happy to sit on that committee to discuss what I think the workflow should be, but I'd like rich lowe, albert lee, and matt to be on the committee to give their thoughts too... I want to have a permission and workflow model that works for everyone if possible. Sergey, can you send out mail about this?

Actions #4

Updated by Piotr Jasiukajtis over 12 years ago

I'm also unable to:
- change the category (
- change the type (for example from BUG to Feature
- I don't see 'Change properties 'MORE')

I use Firefox 3.6.13

Actions #5

Updated by Bryan Horstmann-Allen over 4 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF