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!


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
Community Members
Community Events
Community Groups

What is the best way to set up a customer when they are associated with three different projects?


I have a customer who is associated with three different projects. I have them grouped together all in one group but two different organizations. What do you think is the best way to set them up? Should I make 1 group consisting of all of the same customer accounts and then three different organizations, one for each of the three projects and name them accordingly? Is there any tool or a better way to set this up? Just trying to get someone's opinion on the matter.


1 answer

Groups are cross project - for licensed users (customers with portal only access cannot be added to groups)

Organisations are created within JSM project.

I would stick to organisations, but if they need to be involved with some software projects, then maybe I would think about adding some project role instead of using groups. It would be managed on project lvl similar to organisation, without admin needing to change group access if something changes.

Hi Lukasz,

My company uses JSM more like an IT tool to resolve customer tickets and issues. I invite these customers to Jira, but do not give them a license as we have a limited number. We only give licenses to internal folk. I add these customers to groups because if these customers are associated with other projects and something changes I can make the changes easily and it is a nice way to organize everything. I don't understand what you mean groups are only for licensed users. I have created groups and added customers to those groups, but the group only has customers, no internal folks. Please explain further.


I was digging and it looks like turning customers into users is possible, without increasing license size

Customers need to be migrated into Atlassian accounts, as explained in this thread: 

So, with that in mid, I would probably go with matching groups & organizations for each customer.

(It probably could be even 'simplified' to only groups, but then it could trigger additional changes in JSM eg. default shares with organization, so in my opinion it wouldn't be worth it.)

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events