Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Allowing customer A to see Components 1,2,3 and Customer B see Components 1 and 3

Sandeep Banga July 24, 2023

Hello, we use Jira Service Desk Cloud. We have created a customer portal and display a list of components to customers. The components correspond to products we sell.

Since not all customers use all products we sell we would like to only display relevant components to the customer.

We use one project for all customers.

Is there a way to control the list of components based on the customer? Attached is a pic of the components list displayed on the portal.

 

JIRA SERVICE.jpg

 

Thanks! 

2 answers

1 accepted

2 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 24, 2023

Welcome to the Atlassian Community!

No.

Customer's visibility of requests is entirely based on their organisation, you can't do it off other fields, and you can't limit field option by person, only by project (and issue type if it's a custom field)

The best you could do would be to change your components into projects, having one help-desk per component.

Sandeep Banga July 26, 2023

Thanks! We are using one project for all customers since it is easier to manage. If we want to make it more customized then creating separate projects per "something" a customer or types of issues etc. may be the way to go.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 24, 2023

Welcome to the Atlassian Community!

Not directly, customers can only be restricted to view requests by their organisation (people from org 1 cannot see stuff raised by org 2), you can't do it by component, and nor can you offer different component lists to customers.

You can get a bit closer to this with a bit of a restructure, but I suspect this is not going to fit with your systems.  Change the components to be the projects, and have separate help-desks for each component.

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