Feature #4309


create a special role for clients

Added by Diana Susca over 14 years ago. Updated about 14 years ago.

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


Estimated time:


The client should not see the inner-workings of the projects:
When he adds an issue, he should only set the version, the priority, the category of the issue.
He should not know who it will be assigned to, or what are the names of the possible assignees - or he should see as possible assignees members of a "support group". He shouldn't know the names of the project members.
He should not have be able to set a start/due date, but if they are set, it's all right if he could see them.
There should be two "threads" of conversations over the issue: The notes/questions that the client exchanges with the developers, and the notes that are exchanged between developers - the client should not have access to that conversation.

So it's sort of a "blind" user - just issue poster, with very limited (customizable) views.


_form.rhtml (3.35 KB) _form.rhtml Modification of issue form Matthew Connerton, 2010-01-12 03:51
Actions #1

Updated by Robert Chady over 14 years ago

I doubt this type of functionality will ever make its way in to Redmine core. Most of what you want can be done with a custom plugin that overrides the various views based on your own specific needs. The issue is that this is very user specific. If you need this type of customization, your best bet is to take some of the plugins that exist already and include them with your own custom modifications in a plugin.

Actions #2

Updated by Jean-Philippe Lang over 14 years ago

  • Category changed from Groups to Issues permissions
Actions #3

Updated by Michael Koch over 14 years ago

Cant you just set up a Role for that?

Goto your admin settings -> Roles & Permissions -> New Role

Actions #4

Updated by Robert Chady over 14 years ago

What he is asking for requires custom work that just creating a role does not give you. Sure, you can create a new role, but it does you little good when the desired functionality as described in the initial posting is not controllable by just permissions.

Actions #5

Updated by Andrea Saccavini over 14 years ago

The role "client" is very interesting for me too and it can not be made using permissions.
Another feature connected to the role is the possibility to enable e-mai notification in relation to the states the client can view.

Actions #6

Updated by Diana Susca over 14 years ago

yes, I think it is a very specific request, it was a long shot to ask for it :). initially i thought of a plugin but I saw that there were none to match this, and I have no idea what ruby is about so I can't implement it myself.

roles can't restrict the items a user can see in the interface or the content of the drop-downs.

Actions #7

Updated by Alain V. over 14 years ago

I have the same type of request about this blind user.
That type of user is a need for me.
Considering this feature is not to be considered, any suggestion of useful plugins to set this type of user?

Actions #8

Updated by Matthew Connerton over 14 years ago

I have "accomplished" this by creating a role "Client" and then modifying the issue view in /app/views/issues/_form.rhtml and added snippets of code such as:

<% if != "Client" %>
  [html i don't want clients to see]
<% end %>

However, I am NOT a rails developer in the least and am sure this is a more graceful way of doing this. I am just ignorant to it. I have attached my _form.rhtml file for reference. It would be nice if someone could point us in the right direction for correctly modifying the view.

Actions #9

Updated by lori dunkin about 14 years ago

I have a need for a client role as well and have setup a special role for this but would want this role to only see issues they create or get assigned and none of the issues between the rest of the project team.

When I add this "client role" into a project, they have the ability to view all issues.

My current workaround is to add a specific project for just "client requests" and create duplicate subprojects but that requires a lot of moving tickets back and forth and doesn't seem as elegant as being able to simply have a role that can only see tickets they initiate or are assigned.

Actions #10

Updated by Oleg Volkov about 14 years ago

You can create a subproject and for each issue the client to create a issue in the subproject.


Also available in: Atom PDF