Customer permissions JIRA

[Muhammad Bilal]

Hi,

We have couple of projects on the JIRA CLOUD, some projects need to be open for the customers who are random and unknown email address, some projects are enabled with the option only, customers my team adds to the project can send the request only.

Now the problem is when i enable the option ''ANYone can send a request without logging in'' i can receive the tickets on our jira service desk, but on our main portal of the atlassian the project is open, i do not want this way, i want the project to be hidden on the main portal and only the customers for his specific project should see his project, how should i do that. Have been searching every thing, but could not find any solution till now.

Required help urgently.

Thank you

[Jack Brickey]

I’m trying to understand what you are stating here. I will capture what should be happening and why in hopes that we move closer to an answer for you.

you have two projects: A-Private and B-Public

if anyone goes to the main portal UR” they will all see B-Public but only those individuals that are listed as Customers of A-Private will see that project. 

Example:

Jack is a customer of A-Private - he will see both projects in the portal if he is logged in. If he is not logged in he will see only B-Public

Sally is not a customer of A-Private - she will only see B-Public

this is the way it should be behaving. Is this consistent with what you are seeing?

[Muhammad Bilal]

Hi,

Yes exactly as you described in the above response, let me try to explain again what is happening with the screen shot,

1) I have only 1 project xyz, the settings on the ''customer permissions''  is '' Customers my team adds to the project'' are added only can raise a request.

2) I have 20 plus other projects, the settings on those project is ''Anyone can send a request without logging in'' because we have unknown customers, so we have to enable this option.

3) Now when we see our portal which is https://xyz.atlassian.net/servicedesk/customer/portals , here all the 20 projects which are on the setting 'Anyone can send a request without logging in'' are visible. So when the customer(service desk customer) for the 1 project xyz, login on the portal, he can see all our other project names, email request types, we do not want this to be open, in simple words, i want all these 20 open project to be hidden on the main portal.

4) Looking forward to hear soon, it is very critical situation for us!!

5) If required i can share my phonenumber or email to contact you directly. i have already raised a ticket on the support atlassian as well, but waiting for the answer.

Thank you

[Muhammad Bilal]

[Jack Brickey]

Duplicate post

This is working as designed. Since the 20 public projects are just that “public”, anyone that goes to the portal will see those projects. There is no concept of “blacklist” that would exclude specific customers from public projects.

[Muhammad Bilal]

Hi again,

I would like to add few more details:

We have two types of projects:

1. public projects with e-mail as exclusive channel. The web portal is not used for those cases.

2. private projects with web portal as channel only. The e-mail is not used for those cases.

Our critical issue is that the customers who have access to the private projects, are viewing also all other public projects.

Into our company, we are providing many services to different customers. With the current setup we have, all customers (with access to the private projects) can see information that they shouldn't.

Considering our constraints, can you please provide to us the most adapted solution we can have with Jira Cloud?

[Jack Brickey]

Unfortunately my answer remains the same. If you want you can reach out to Atlassian Support to get their input and/or provide feedback. If you do, please reference this thread so they can catch up on the conversation. There may be suggestions already open for similar requests. But unsure how a solution would be implemented TBH.

[Muhammad Bilal]

@Jack Brickey  thank you, i have copied this thread and pasted on the Atlassian support on the ticket which i have already opened. 

BTW i found a similar case, looks like this issue has not been resolved 20/feb/2015

https://jira.atlassian.com/browse/JSDCLOUD-1547

Thank you

Muhammad Bilal