You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Is it possible to create different portals for clients within 1 project. It is completely illogical for each project to have a portal, why work with many different projects for customers?
It basically implies Jira expects a company to have a complete separate support team for each client, why create silo's like this?
Also it is repetitive, to have a list within the portal for specific questions and then another list when clicked on the portal group, which genius thought about that?
The most common use case would be this, and this is what im looking to achieve:
You have a Service Desk Project with different Queues for different projects/clients. On the customer facing part you have the help center, and for each help center you have a service desk project. In each help center you have what is now a "Portal" for each queue and then you segment the question if its a bug or feature request on a list. Thats it, the most simple thing and its just not possible.
Is there any way?
Thank you for your response, i just cannot fathom this design decision. It doesn't make sense to me. Im aware of all the streamlines, and im wondering if this could be a solution to my problem:
- Can i restrict based on the logged in user which portal group they can see in a portal.
My problem is that its completely unprofessional to show clients all of our other clients. This should be able to be restricted. This even tho its an inconvenient way for the client would solve my issue.
I am afraid you have been slightly mis-lead, or talked at inaccurately, by a 'bot.
You are absolutely right that a client should not have access to other client information (unless you choose to allow it), and JSM supports this.
Your clients should be set up as "customers", and grouped into "organisations". You can get a bit clever with the organisation stuff, but the most basic idea of these is that "people in org X can see other stuff from org X, but not any other org". The default is "only see my own requests", but it's a simple tick-mark to make it "my org", and a few more to make it "everyone"
Im just talking about the help desk side, so the customer facing raise a request side. Within this setup i'll be able to need to segment portal groups, because a customer is a portal group.
An Atlassian consultant actually advised us to not use a new project for every customer (which is logical) but Jira does not support segmentation of portal groups or any segmentation within a project on the customer facing side (also very, very limited customization within portal groups).