Jira Project access by clients to only one project related to the client

Ruben_xsznll

Hi,

 

For a couple of months we're using Jira. We use classic projects and work on multiple projects with multiple teams. Some of the team members are external and are not part of the internal core team of our company.

 

I'm looking for a solution for the next problem.

 

External Client A + internal team

needs access to Project 1

External Client A is not allowed to see access to other projects 2 and 3. Internal team is allowed to see the other projects.

 

External Client B + internal team

needs access to Project 2

External Client B is not allowed to see or access other projects 1 and 3. Internal team is allowed to see the other projects. 

 

Internal "project"  C + internal team

needs access to Project 3

The internal team is allowed to see the other projects.

 

Import note here is that the external client or external team members are able to make new issues, epics, bugs, and etc..

 

I tried to follow this tutorial, it helped very well and the external clients are able to see their own project but not the others. So far, still good. But the client cannot create new issues for example. Because this external client or teammember can be a Product Owner, this is needed.

https://community.atlassian.com/t5/New-to-Jira-articles/How-to-give-a-user-read-only-access-to-a-single-project-and/ba-p/1010143 

Can someone tell me how the external clients/team members are allowed to make issues and etc. like if they are an internal team member.

[EDITS] 01: I think the best way is to edit the permission schemes and add the project role Clients to edit/create/ issues. 

Best,

 

Ruben

Andy Heinzer

Hi Ruben,

It looks like you might have already found an answer here, as you have edited this question to indicate as much.  In the future, rather than just edit your question, it would be helpful to others with the same question to post an answer to it instead.  You can answer your own question here.  Accepting an answer to a question will mark the issue as solved, which can help search engines to prioritize such questions in results that might help others find solutions faster.

Certainly, the managing project permissions documentation can help any type of Jira project to accomplish the basic idea here of restricting access to projects.  However since we know you're using Jira Service Desk, there are a few differences to be aware of.  First is the distinction between user roles in Jira Service Desk. These are noted in Jira Service Desk: Agents, Customers, and Roles.  The important thing to note there is that users that are only in the customer role, are not licensed Jira users and only have access to the Customer portal.  That usually limits them in regards to what requests they can created.  Technically they can't create all the issuetypes in Jira, only requests in the customer portal that can be represented as issues.  More info on that in Jira Service Desk: Issues vs. Requests.  There is a related document over in Set up customer permissions in order to more thoroughly complete the customer permissions here.

I hope this helps, feel free to submit your own answer if you like.  If this helps, you could also accept this answer.  Let me know if you have any followup concerns.

Andy