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; } } }

Make different issues within the same project visible to different customers in the portal

Anna Debono

Hi,

So I am building a service project for our Procurement Team. Within this project, I would ideally like to have 2 issue types; Supplier Contact and Customer Contact.

However, when logging into the Customer Portal, our Suppliers should not be able to see and create a Customer Contact issue and vice versa.

Is this in anyway possible?

Thank you in advance for any input and guidance.

Anna

Accepted answers

Kris Dewachter

Hi @Anna Debono ,

Unfortunately, you can not set permissions on the request types in the portal.

If a customer has access to a project in the portal, they will able to see all request types.

I think in your case, your best options are to:

Create separate JSM projects in your portal, with different permissions
Add some explanatory text to the requests, making it clear who can make the request
Create an automation rule that automatically closes a ticket when created incorrectly.

Best regards,

Kris

All comments

Kris Dewachter

Hi @Anna Debono ,

Unfortunately, you can not set permissions on the request types in the portal.

If a customer has access to a project in the portal, they will able to see all request types.

I think in your case, your best options are to:

Create separate JSM projects in your portal, with different permissions
Add some explanatory text to the requests, making it clear who can make the request
Create an automation rule that automatically closes a ticket when created incorrectly.

Best regards,

Kris

Kleber Pauta - ReleaseTEAM

Hey Anna,

I recommend splitting up the 2 issue types into 2 separate projects. Once that is completed, follow this Atlassian documentation piece to limit visibility into each project.

Becky Brooks - MCP Gateway for Jira

Hi @Anna Debono ,

An alternative to creating different projects in JSM is to create different views with your Jira data within an app like Visor.

You can import Jira data, filter out what you want to display, and then decide who gets access to which views. Visor is commonly used for sharing Jira project data with external stakeholders in a customizable way.

You can find more info about Visor in the Marketplace:

https://marketplace.atlassian.com/apps/1226209/visor-flexible-spreadsheet-for-jira-roadmapping-bulk-edits?hosting=cloud&tab=overview

I hope that helps!

Take care,

Becky @ Visor

Anna Debono

Hi all,

Thank you for your replies.

I kind of figured, that it is not possible but was hoping that there is something that I am not thinking of.

Of course, creating 2 separate projects would be the way to go, but this is exactly what I was trying to prevent --> I would prefer if the team only needs to work in 1 Service Desk and not have to monitor 2 different ones.

But alas....

Again, thank you all for your answers. Have a lovely day!

Anna

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-cloud

jira-service-management