How do I configure private, per-vendor projects?

Question

We're evaluating JIRA cloud and I have some questions about setting up a specific type of project and permission scheme. We are a application/services shop and will have several projects that all of our teams can collaborate openly on.

However, we also need to setup a project-per-vendor where we can invite limited persons from our various vendors to open issues or respond to our questions. I don't want them to see any of our internal projects or other vendors' projects.

I'm worried that the permissions scheme to maintain this kind of setup will become a nightmare... am I right?

We'd have to maintain an internal-users group, a group-per-vendor, and assign permissions/schemes to view projects like:

* vendor bar project: internal-users, vendor-foo
* vendor bar project: internal-users, vendor-bar
* internal project qux: internal-users

Phill Fox · Answer

Hi @Anthony Mastrean

The management of the approach I suggested is relatively simple (and with the right permissions) is delegated from the system administrator to the project administrator. The only action once it is setup is to add/remove users from the role on the project.

James Strangeway · Answer

Right.  It can require some overhead.  Like each project does require us to create a new group for stakeholders, but we have one dev group for the majority of our projects, which we just have to assign to the developer role.  Does not typically require us to move people in and out of the dev. group.

eacwpku · Answer

This sounds about right, but requires constant maintenance. Every new internal team member has to be explicitly assigned to the correct group and every new project has to be assigned the correct scheme.

I was hoping there was an explicit feature for privatizing a project or limiting a user's view that required explicit action only on those projects/users.