Project

General

Profile

Actions

Feature #393

closed

Role that can't assign a ticket

Feature #393: Role that can't assign a ticket

Added by David Petersen over 19 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues permissions
Target version:
-
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 3 (0 open — 3 closed)

Related to Redmine - Feature #444: submit issue via emailClosedActions
Related to Redmine - Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory ClosedActions
Has duplicate Redmine - Feature #8129: Role that can't assign a ticketClosedAzamat HackimovActions

Updated by Ed Ed about 19 years ago Actions #1

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

Updated by Thomas Lecavelier over 18 years ago Actions #2

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

Updated by Nikolay Solakov over 18 years ago Actions #3

+1 from me too :)

Updated by Daniel N over 18 years ago Actions #4

me too.

Updated by Thomas Löber over 18 years ago Actions #5

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.

Updated by Paul Voelker over 17 years ago Actions #6

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

Updated by david austin over 17 years ago Actions #7

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

Updated by david austin about 17 years ago Actions #8

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

Updated by Robert Cermak almost 17 years ago Actions #9

+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…

Updated by Rick Bird over 15 years ago Actions #10

Issue is definetely a must.. +1

Updated by Etienne Massip over 15 years ago Actions #11

  • Category set to Issues permissions

Updated by Kioma Aldecoa about 15 years ago Actions #12

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

Updated by Kioma Aldecoa about 15 years ago Actions #13

  • Assignee set to Jean-Philippe Lang

Updated by Kioma Aldecoa about 15 years ago Actions #14

  • Assignee deleted (Jean-Philippe Lang)

Updated by Terence Mill about 15 years ago Actions #15

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

Updated by Daniel Felix about 14 years ago Actions #16

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

Updated by Daniel Felix about 14 years ago Actions #17

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

Resolved in #8050.

Updated by Daniel Felix about 14 years ago Actions #18

  • Status changed from Resolved to Closed
Actions

Also available in: PDF Atom