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,462,886
Community Members
 
Community Events
176
Community Groups

Separate sites for different deps in one organisation?

Edited

Hey together,

 

just a quick question for you experienced Jira admins:

 

We have a Site for IT-Support purposes. Multiple projects inside, all IT, service desk, e-commerce, process management and so on.

 

Now we got the request to add

  • our marketing department for project planning
  • our facility management for service desk and project planning

 

Now I am stuck at this point:

  • If I use the existing site, I have to pay the addons for all of that new users, even if they dont want to use them. (Bigpicture, Confluence, Reminders, EazyBI)
  • If I use the existing site, I have to pay the Jira Service Management Price for all that users, even if the "only" use the Jira Work Management (which costs 5$ instead of 20$)
  • If I use a new site, I will maybe get problems to maintain multiple sites, permission schemes, workflows, etc.
  • maybe more?

 

What would you do in this case? Maybe somebody in the same situation here?

 

Thanks in advance!

David

1 answer

1 accepted

1 vote
Answer accepted
Laurens Coppens Community Leader Jun 30, 2021

Hi David,

 

Point 1 is correct, if you add additional users they will count for the addon license.

Point 2 on the other hand is not correct, you can give users a JWM license without giving them a JSM license, that way you only pay for JWM, and they will be able to use the JSM portal but not the JSM backend.

So for marketing you only need JWM.

For facility, they will need JSM as they need a service desk.

You could choose to do the project planning of facilitity in the JSM project as well, so that they don't need a JWM license - but this depends on their needs.

 

Creating a new site could also mean additional costs like duplicate addons, or users that need a JSM license in both sites.

 

Based on the limited information i have, my guess would go to just adding them on the same site, and grant them only the license they need.

 

Hope this helps,

Laurens

Jack Brickey Community Leader Jun 30, 2021

Agree. Also note you mention confluence confluence is a product and it’s not an add-on so you don’t have to pay for that unless you give users access to it

Like Laurens Coppens likes this
Laurens Coppens Community Leader Jul 01, 2021

@Jack Brickey  I completely missed that, thanks for pointing that out!

Confluence is like JSM and JSW a product and not an addon/app so you can choose who you give access/ a license.

Thank you for the response. You're right, I missed that Confluence is a separate product.

 

I will put them in the same site with our it-projects.

And if I book JWM it will appear as own product like Confluence does?

 

Thanks.

Laurens Coppens Community Leader Jul 02, 2021

Yes, JWM will also appear as a seperate product.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events