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
We are a support / development organisation with a number of clients.
We would like to implement JSD for our org. How do you support such scenario?
Would you create multiple jira projects one per customer ?
This makes the support staff's life difficult because they need to go through each project separatly? IS there a better way?
I think a single project is not an option because clients cannot see each others' issues.
Hi @Gábor Faludi ,
Customers in Jira Service Desk can be grouped into Organizations, and if set up, can be allowed to share requests created with only other Customers within their Organization.
Using this approach, you can have a single JSD project for many different clients.
Please see this article for setting up Customers: https://confluence.atlassian.com/servicedeskserver/managing-access-to-your-service-desk-939926273.html
More info on JSD roles: https://confluence.atlassian.com/servicedeskserver/setting-up-service-desk-users-939926312.html
Hi @Jennifer Kharrazi , it's been a while since I've configured JSM so assuming that nothing has changed, yes absolutely.
An organization is something you can configure within a project. Let's say we have two clients from two different companies who will be raising requests:
Within my service project, I would create two organizations: ParisCorp and VIC. The respective emails of the users above would be added to each.
When email requests are configured for my project, it will allow both Amy and Frank to generate requests by sending an email to the same mailbox, but due to the fact they belong to different Organizations, their requests will be hidden from one another.
Onboarding a new employee: John R. (email@example.com) and adding him to the correct Org means that I can make his requests available for Amy to view and vice versa.