nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can a subset of a team use Jira premium or does it need to be ALL users?

Kate Brigham_rz3i80

I'm trying to figure out if just a part of our team could upgrade to Jira premium to make it more affordable vs. having to upgrade the full team?

Thanks for letting me know if that's even an option, and if it is, does it work, or does it create a hot mess?

Accepted answers

Dave Mathijs

Hi @Kate Brigham , welcome to the Atlassian Community!

The Jira plan is valid for all users, so there's no option to have part users on the Standard Plan and other users on the Premium Plan.

All comments

Dave Mathijs

Hi @Kate Brigham , welcome to the Atlassian Community!

The Jira plan is valid for all users, so there's no option to have part users on the Standard Plan and other users on the Premium Plan.

Kate Brigham_rz3i80

Good to know, thanks!

Rob Horan

You can set up two sites but then the teams will be completely isolated.

Michael Diaconescu_8d8nfs

In that context, can issues (epics, stories, tasks, bugs etc.) be shared/viewed across the two sites, or not? That is, can some of the teams have their plans created and managed in the first site (Standard license), and the leadership team and project managers to create the advanced roadmap in the second site (Premium license) by using the info from the plans created in the first site? Thanks!

Johannes Waldheim_9m6apb

Very good point!

Patrick Wright

I can guess the answer to this question, but why not? Jira Premium is fairly expensive (compared to other plugins) but only a handful of the users on a Jira instance will actually use its features (team leads, product owners, upper management, etc.). It just doesn't make sense for me to have to pay a large amount for users that aren't using those features.

Tori Hermione Baker

Just hit the same issue, @Patrick Wright . I have external users that only need to access one project. To improve the ease of this I have created a Team Managed project away from the portfolio isolating its instance (just for ease of access management). Even though the users will only access one project, and have no cross-team dependencies, why can they not have a standard plan? It's a question of why not as to Patrick's point, as now I will have to double the cost and set them as premium, which is rather frustrating as they meet the criteria for one.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud