Isolate team-based projects

STX November 20, 2023

Hello,

we have multiple team-based projects, which should run as isolated as possible. Right now, users in one project can see accounts that are members of other projects by clicking on the "Add people" button. There you can see any account that is part of one of the projects.

Is there a way to isolate the projects without going company-based?

It's actually astonishing what a GDPR-hellhole these atlassian products are without in-depth and time-consuming configurations.

1 answer

0 votes
Ste Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 20, 2023

Hi @STX 

Not that I know of, natively.

With the appropriate global permission to browse users, you can see all users on the site through search boxes like this.

What's the need for this? Perhaps that'll help drive an alternative option :)

Ste

STX November 20, 2023

What's the need for this? Perhaps that'll help drive an alternative option :)


Protection of privacy and GDPR compliance. I dont see the need for normal project members to be able to view the names of members in other teams/projects, they are not involved in.

I assume the only way around this are company-based projects and in-depth customization of the permission schemes.

Ste Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 20, 2023

Hi @STX 

Sounds like a specific use case; Jira's designed to allow for self-sufficient management of user access for Projects - which requires them to view and add users from the licensed user list.

Users will still be able to go to "People" in Company-managed Projects and view a list of users to add to roles, or select from a user picker with a full list of users (aside from Assignee, which requires a specific permission).

But yes, editing a Company-managed Permission Scheme is probably most optimum for the direct need. For example, you could create a Permission Scheme which provides access based on a Group?

Ste

STX November 20, 2023

Well, the access part isn't the problem. The problem is users being able to view any name of any user within that Jira instance. That is a huge GDPR violation. Are you sure there is no way at all to limit visibility to only the users that are actually part of that specific project?

Ste Wright
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 20, 2023

Hi @STX 

It looks like improvements are rolling out for this, after a bit of searching I found this discussion which seems to be somewhat aligned to your need.

As it'll be a new feature, I'd recommend contacting Atlassian Support to confirm if it's available on your instance, and how it will work to confirm it meets your requirements :)

Ste

STX November 21, 2023

Thanks a lot

Like Ste Wright likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events