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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,816
Community Members
 
Community Events
176
Community Groups

Permissions for a user to access tickets from all different organizations

Hello,

I have a single project and within that client I have 6 different organizations that were created here:

https://xxxxx.atlassian.net/jira/servicedesk/projects/EVDDGE/organization/

I want to assign all rights to a specific user (customer) to see all tickets from all 6 different organizations.

For now, he only sees tickets from the organization that belongs to him.

How to make ? What's the best way?

 

Should I invite the same customer in each organization or is there another method?

 

Thanks in advance,

Best regards

1 answer

0 votes
Mark Segall Community Leader Dec 06, 2022

Hi @KDSI Sàrl - The best way to handle this is by adding that customer to each of the 6 organizations.  They would then have visibility to any requests that have been shared to those organizations.  

Caveat - When a customer is tied to one organization, the issue will automatically share with that organization.  When a customer is tied to multiple organizations their share setting will default to "Do not share".  So, you have a couple options:

  1. Change Management - Instruct this "power customer" that they will need to be cognizant of selecting an organization so people within their own organization can see the requests they submit.
  2. Separate Customer Account - Consider a separate "admin customer" account that they use for viewing requests vs. their personal account that they use for raising requests.

Hope this helps.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events