What's the best way to secure projects/groups/issues by client?

[Deleted user]

I work in a professional services organization and thus, we use Jira for some of our client billable projects as well as internal projects. Naturally, we want to secure our clients projects from each other such that, one client cannot access the content of another client. In working with Atlassian Support, I was advised to remove the Browse Projects permission from all-logged-in-users in the permissions scheme and to assign that as a project role. That works, however I then discovered that users with the Member role on a project are not able to tag each other (like, the @name feature in comments). We are disappointed about this. Atlassian Support says that the Browse Users and Groups is also a global permission.

Is Jira simply not the right product for our use case? Is there no way to offer a non-crippled Jira to our project teams that want to invite in client users to the Jira project without exposing other clients projects?

[Nguyen Tran · Accepted solution]

Hi Neil,

You can go to Jira Admin > System > Global Permission. The "Browse Users" global permission is what allow your users to see other users' profile and @mention them as well as other features involve a user picker field.

If you are worried about your clients seeing other client's profile, I'd suggest trying out Jira Service Desk as it has more customized permissions around Customer Role.

[Deleted user]

That's what I was afraid of. Jira is not the right product for our use case. 

[Nguyen Tran]

It really depends on the problem you're trying to solve. The 2 products (Jira Software and Jira Service Desk) supports each other nicely. While your devs team use Jira Software to manage their projects/products development, support team can use Jira Service Desk to support your clients and link support tickets to bugs/features on your devs team's projects for a better context or involve your Devs on solving a support ticket.

[Jimmy Van (GLiNTECH)]

Hi Neil,

Normally I would go with the above options.

Alternatively, perhaps check out Zones https://marketplace.atlassian.com/apps/603936/zones?hosting=server&tab=overview and then set up the relevant zones. This would require you to either host Jira, or if you're not interested in running servers, perhaps work with a managed service provider.