Can we have different licenses at different hierarchy level in a company that has to be independent?

[naveen chowdary]

Hi Atlassian community,

We’re setting up a Jira for Multilevel organization with the following Structure.

Level 1: Company

Level 2: Divisions (e.g., QMS, V&V, Program management, SW Development team)

Level 3: Projects under each division.

Right, here are my questions:

Let’s say we are planning to purchase 100 Jira licenses

• Can we have these licenses in such a way 

For example,

QMS team (with QMS plugins)

Program managers (with Advanced Roadmaps)

V&V Testing (With Jira Service management)

SW Developers, testers (Jira Software)

Again, these Licenses has to be independent and cannot be influenced by top level licenses  and their plugins 

Picturization for reference

and also, can we Restrict or allow access to Projects/Divisions with the same base license depending on hierarchy level.

[Trudy Claspill · Accepted solution]

Hello @naveen chowdary 

Welcome to the Atlassian community.

I'm not sure that I fully understand your question, but I'll try to answer it.

First the product are installed on a Site which is identified by a URL; i.e.

https://yourCompany.atlassian.net

You can have one copy of each Atlassian product per site.

It is possible to have multiple Sites grouped into an Atlassian Cloud Organization, depending on your licensing plan, or you can have a separate Atlassian Cloud Organization for each Site. 

Next Jira and Jira Service Management currently can be licensed separately but coexist on a single site. So you can license Jira (getting "software" and "business" project templates) for X users and license Jira Service Management (getting "service" project templates) for Y "service agents" plus unlimited "customer" type users.

Alternately you can have two separate sites; one where Jira is deployed and another where JSM is deployed.

With regard to plugins (i.e. apps from the Atlassian Marketplace) those typically apply to a Site and a Product. The specific licensing option for an app depends on the app, but generally an app license is acquired for the same number of users as the product. If you have Jira licenses for 100 users, then each app/plugin is also licensed for 100 users.

(There is some work in progress to provide more licensing options such as licensing an app for a subset of Jira users. Those options would have to be implemented by the vendor of the app for their app.)

When you have Jira and JSM coexisting on the same site, the licensing for apps has required the user license match the larger of the licenses between Jira and JSM. If JSM is licensed for 50 agents and coexists on a site where Jira is licensed for 100 users, then apps had to be licensed for 100 users.

The ability to limit the functionality provided by an app to a subset of users depends on the app. Some apps include a permission model that enables you to limit who can access the functionality provided by the app.

Advanced Roadmaps is a native feature in the Jira Premium subscription. You would have to have at least the Jira Premium subscription to get that functionality. It does include a Permissions module so you could limit who has access to create Advanced Roadmaps plans and who can see those plans.

Within Jira (and JSM) data/items/issues are grouped into Projects. Projects have Permissions configurations that determine who can see and interact with the data in the projects. So you can restrict who can interact with the projects.

There are a number of question I would have about the model you are trying to implement in order to provide a more relevant and detailed response. I encourage you to consider contacting Atlassian Licensing directly about these questions, or consider working with an Atlassian Solution Partner that provides licensing services to help you determine the license model that will work best for you.

[naveen chowdary]

Thanks @Trudy Claspill for your solution.

Now it triggered two more questions in my mind, and I hope you answer them to the point as well.

1) As mixed plan of different licenses within a same instance is not possible. What is the way to go to fulfill our above Multiple tool license requirement with optimal cost (Note*: having two or more instances may incur huge costs)

My option: upgrading all 100 instances to premium but it will expel QMS and Big picture requirements out.

Other similar options 

(Upgrade all 100 instances to big picture or QMS - incur huge costs) 

2) Do we have any other PM tools to meet our requirement of having mixed tool licenses within the same instance 

Kindly pls provide your suggestion to deal with this effectively. You help would be highly appreciated.

[Trudy Claspill]

I can't answer your question about a setup that provies optimal licensing. I don't have enough information about either your requirements or all the licensing options that are available.

I agai encourage you to speak directly to Atlassian's Licensing team or an Atlassian Solution Partner that handles licensing so that they can dig deeper into your requirements and provide an answer backed by applicable research. I am not directly involved in managing licenses for any company so the only information available to me is what you could find by searching Atlassian's site.

You might want to consider an Enterprise license plan. That would enable you to have a single Organization that has multiple sites under it. In that model one option is to pay for each unique user only once for each Atlassian product to which they will be granted access across all your sites.

I don't have details on all the options and pricing for such a plan. I have worked with clients who have Enterprise plans where they have some sites using products under the Enterprise plan, some on Premium plan, some on Standard, and some even on Free. I have also heard that some of the new app licensing models under consideration include how to license an app for unique users across an Enterprise Organization rather than per site. Some combination of those options may be more cost effective for what you want to achieve.