[EAP 5725]: Project roles feedback

The new project roles seem to work quite nice so far. Here's some initial feedback:

- Why are there roles like "All projects viewer/administrator/..."? I find this quite confusing
because when I wanted to assign the role "Project administrator" to a user, I tried to find
something like "" in the projects dropdown until I realized that this is a special role. Changing this would IMHO be more intuitive and make the list of available roles more concise. - A cosmetic issue: The role "System administrator" (and "Agent Manager"?) actually doesn't apply to any projects, yet the table in "Roles and Permissions" lists "]]>" for it. Just leave it
blank or display "n/a".

- Adding roles for several projects is a pain. It should be possible to create role/project
combinations by using multi-selection enabled lists for the projects. This implies that there should
also be a way to edit the assignment of a role to one or more projects.

- While configuring some roles, I realized that this would be significantly easier if TC had the
ability to put projects into groups and I could assign roles to those groups. Is something like this
already planned?

Sascha

1 comment

Hello,

Many thanks for your feedback, it is very improtant for us.

In TeamCity role is a set of permissions. You can see the whole
configuration of roles and their permissions in the roles-config.xml file
(placed in the config directory of TeamCity). Actually you can change the
set of permissions in each role via this file and server should reload them
automatically. Each role in TeamCity can be either global or
project-related. Global roles are not assigned to any particular project and
if global role contains project-related permissions (like RUN_BUILD) these
permissions are granted to any project in the system. Project roles must be
assigned to a project and their permissions are granted to a user in some
specific project.

- Why are there roles like "All projects viewer/administrator/..."? I find
this quite confusing
because when I wanted to assign the role "Project administrator" to a
user, I tried to find
something like "<All projects>" in the projects dropdown until I realized
that this is a special
role. Changing this would IMHO be more intuitive and make the list of
available roles more concise.


Probably you are right, this could be more intuitive. However it will
require some rework in our roles model. We will see what we can do with
this.

- A cosmetic issue: The role "System administrator" (and "Agent Manager"?)
actually doesn't apply to
any projects, yet the table in "Roles and Permissions" lists "<Any
project>" for it. Just leave it
blank or display "n/a".


The "System administrator" role is global and it contains many
project-related permissions and because all of these permissions are in the
global role they are granted to any project. So actually ]]> makes
sense for "System administrator" role. As for "Agent manager", you are
right, this role permissions are not project related and probably we should
display N/A or something like this for such roles.

- Adding roles for several projects is a pain. It should be possible to
create role/project
combinations by using multi-selection enabled lists for the projects. This
implies that there should
also be a way to edit the assignment of a role to one or more projects.

- While configuring some roles, I realized that this would be
significantly easier if TC had the
ability to put projects into groups and I could assign roles to those
groups. Is something like this
already planned?


We will try to make these tasks easier in the next EAP. We plan to allow to
assign roles to multiple users and several projects at once. However I think
to actually solve these problems we will have to introduce user groups and
allow to assign roles to the groups.

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



0

Please sign in to leave a comment.