nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

No access to view other customer issues

unknown

Hello Everyone,

I have an issue here with my service management project, currently when a user (customer) will create an issue (ticket) through the customer portal they're able to view and edit their own issue but they aren't able to view other customer issues for example.

User A: Creates issue PS-199
User B: Creates issues PS-200

User A cannot view User B's issue he/she gets the following error:

What's strange to me is I have permissions currently wide open on my project as you can see in my next screenshot:

I even had a play in the permissions scheme and modified the:

Browse Projects

Ability to browse projects and the issues within them.

But that didn't seem to have any effect on customers viewing other issues.

Can you guys point me in the right direction? If there's any more info you need please let me know.

Thank you

Accepted answers

Liam Green

Hi @[deleted]

Customer's cannot see the tickets of other customers unless they are in the same organisation.

Using your example, what happens when User A adds User B as a request participant to PS-199 using the 'share with' button?

All comments

Liam Green

Hi @[deleted]

Customer's cannot see the tickets of other customers unless they are in the same organisation.

Using your example, what happens when User A adds User B as a request participant to PS-199 using the 'share with' button?

unknown

Hi @Liam Green

So just ran out a test and it seems User B is able to view the issue once it's shared with them. So we know now that works great! BUT now how do we get all issues open and visible to all users without having them share their issue each time it's created.

Thank you

Dirk Ronsmans

As @Liam Green says,

You currenlty have the option open for customers to share the issue with other people. But the user needs to take the action to share the issue with someone else. Who they can share with, that you have defined as everyone.

A different option is Organisations. When a multiple users are in the same organisation (configurable on your Customers section of your project) they are able to share by default (at creation or later) their issue with the whole organisation.

If you want to share the issue with the whole organisation (as an agent) you can put that organisation in the "organisations" field.

The permissions scheme will have no effect on what you customers can see (except then the servicedesk-portal users group), that only applies to the licensed users.

Edit: you're request to auto share with all users would work if you use an organisation and put all the users in it (doesn't have to be a real name, could be a dummy one just to use the functionality ) and then you can create an automation rule to edit the issue and set the organisation on creation.

Liam Green

@[deleted]I'm glad it worked when you shared it.

@Dirk Ronsmans has given a great overview of organisations above, but if you want a bit more on how to use them then the following link should help:

https://support.atlassian.com/jira-service-desk-cloud/docs/add-an-organization-to-a-service-desk-project/

unknown

Hey Guys,

You both have been extremely helpful, thank you so much I expect given the info provided I have everything I need now. At the moment I've created an automation rule to assign an organization when an issue is created, hopefully my rule works out nicely and I've also added in the "Request Participants" field which I believe is the field that drives the Share feature which Liam you pointed out earlier.

We can mark this as resolved!

Monique vdB

@[deleted]thanks for letting us know this helped! I moved the accepted answer (aka marking this resolved) to the thread that solved your issue. This helps bump the useful content to the top.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management