Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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


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 :) 

3 answers

1 accepted

0 votes
Answer accepted
Kris Dewachter
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 15, 2023

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,


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!


0 votes
Becky Brooks - Visor for Jira
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.
Nov 16, 2023

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:

I hope that helps!

Take care,

Becky @ Visor

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.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events