Project

General

Profile

Actions

Feature #393

closed

Role that can't assign a ticket

Added by David Petersen over 16 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues permissions
Target version:
-
Start date:
Due date:
% Done:

100%

Estimated time:
Resolution:

Description

If you are giving clients access to redmine you really don't want them submitting tickets and assigning them to developers
with out it going through a project manager.

Having the ability to more granularly assign permissions to users would help a lot.
Letting them create a new ticket but not assign it.


Related issues

Related to Redmine - Feature #444: submit issue via emailClosed

Actions
Related to Redmine - Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory Closed2011-04-03

Actions
Has duplicate Redmine - Feature #8129: Role that can't assign a ticketClosedAzamat Hackimov2011-04-12

Actions
Actions #1

Updated by Ed Ed over 16 years ago

This is surely already the case. Create a new class of user and
allow them to issue and withdraw tickets and nothing else.

Actions #2

Updated by Thomas Lecavelier almost 16 years ago

I give a +1 to this feature request: it would be so lovely that only manager or developers could assign issues... :)

Actions #3

Updated by Nikolay Solakov almost 16 years ago

+1 from me too :)

Actions #4

Updated by Daniel N almost 16 years ago

me too.

Actions #5

Updated by Thomas Löber almost 16 years ago

We have to consider that issues can be automatically assigned by selecting a category.

So there should be an additional permission "Select issue category" (besides "Assign issue") which will not be given to the "Client" role.

Actions #6

Updated by Paul Voelker over 14 years ago

My software group would be very happy to have this ability. We are new Redmine users and like what we have seen so far...

Actions #7

Updated by david austin over 14 years ago

we are having problems with anonymous users (who we allow to submit a new issue) they are assigning it to the list of developers and we dont want them to assign issues only submit the problem
so +1 for us also

Actions #8

Updated by david austin over 14 years ago

i would like to reopen this as this is a problem as is spam by anonymous users

Actions #9

Updated by Robert Cermak about 14 years ago

+1
More generally: each role could have configurable list of items available on issue submitting.
It is not reasonable to enable to client to set up e.g. Estimated time, “Done %”, or certain customized internal items…

Actions #10

Updated by Rick Bird almost 13 years ago

Issue is definetely a must.. +1

Actions #11

Updated by Etienne Massip almost 13 years ago

  • Category set to Issues permissions
Actions #12

Updated by Kioma Aldecoa over 12 years ago

This feature would be very useful for our workflow. It facilitates a model where only designated people actually review and assign issues.

Actions #13

Updated by Kioma Aldecoa over 12 years ago

  • Assignee set to Jean-Philippe Lang
Actions #14

Updated by Kioma Aldecoa over 12 years ago

  • Assignee deleted (Jean-Philippe Lang)
Actions #15

Updated by Terence Mill over 12 years ago

This is covered by feature request #8050 : "Mightful workflow field enhancement: visible, read only and mandatory"

Actions #16

Updated by Daniel Felix over 11 years ago

Well this could be also closed. With some changes to the workflow -> field permissions the reporter could be restricted to assign a ticket.

Actions #17

Updated by Daniel Felix over 11 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Resolved in #8050.

Actions #18

Updated by Daniel Felix over 11 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF