Project Grouping

There would be tremendous benefit if project groups could be created for the purpose of assigning roles to TeamCity users. This level of maintenance would make the job of administrators much easier when adding both users and projects to TC. I know that this has been talked about a little in the past, but any update on the status of the topic?

4 comments

Ray,

We are not yet implementing the feature. Once we settle on some particular approach, it will be included into one of the future versions.

e.g. the project groups can be implemented as "folders" or as "tags", both approaches with their pros and cons.

What would you prefer?

Do you think that introducing project groups vs user groups will have more benefits with respect to user roles management?

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Hi Yegor,

I definitely think that Project groups would be the first necessity. Hopefully with that implementation, we would also see a way for users to expand/collapse a project group on the Projects page of TC. This would make the view easier for users, especially admins, who hold roles in multiple project groups. Also, if only Project OR User groups were to be implemented, my vote would be for Project groups. This way, new team members could simply be assigned a role in whatever Project groups their team was working on. Also, when a new project is added to TC, it could be added to an existing Project group and their would be no need to configure any user roles to enable access to the project.

Ideally, I think that both types of group could exist. Individual users could be assigned roles directly on projects/project groups, or they could be assigned to (multiple?) user groups, each having its own role assignments. Additionally, projects could still be grouped, although I think that a project should not be able to belong to multiple groups. In this scenario, if a user was assigned multiple roles on the same project/project group, that users role would take in all of thier highest assigned permissions for the project.

When you ask about implementation, what do you mean with "folders" or "tags"? What would be some of the pros/cons of both?

I (and I think many others) would love to see this feature soon. Any thoughts on how any of this functionality might be created through a plug-in?

Thanks,
Ray

0

Ray,

Thank you for your thoughts.

>When you ask about implementation, what do you mean with "folders" or "tags"? What would be some of the pros/cons of both?

"Folders" approach suggests each project belongs only to a single group. Users can be assigned roles in a group, so that adding a project into the group grants group permissions to it.

In the "tags" approach, a project can belong to multiple groups, most probably there are no roles associated with the group, this is rather a UI notion that lets easily filter only the projects by some tag and assign roles for the filtered projects.

From your notes, it seems "folder" approach will better suit your needs.

Here is the issue addressing projects grouping in UI:
http://www.jetbrains.net/jira/browse/TW-705

And this one addresses projects grouping in notifications that is probably similar in problems to roles assignment:
http://www.jetbrains.net/jira/browse/TW-3882

You can watch/vote for the issues.

I cannot figure out how this full functionality can be implemented via plugin, but I believe a plugin can help to solve (maybe in somewhat hack-like way) some specific administration problem.

--
Best regards,

Yegor Yarko
Project Manager
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

0

Thanks for the reply. I'm looking forward to seeing this feature.

0

Please sign in to leave a comment.