Activate Jira Premium on Trial period and only for selected group of users across an organisation

[Michael Chuong]

Hi, 

We have a small number of users wanting to user premium version of Jira given we are currently on standard version with < 300 users.

I would like to trial out the premium version on the selected users (having different Jira roles) within our organisation on a single site.  

Once the trial period is finished and satisfied, we still want to only have these users using the premium version while the majority of users continue to use standard version.

Please advise if we can activate the trial period on selected individual accounts only?

Regards

Michael

[Michael Chuong]

The features in premium version will not be applicable to the majority of users.  Only a couple of manager-level users want the extra features.  

But if it is visible to all users and have no operation impact on existing projects with standard version, that is still fine too during the trial period. 

Only on buying the premium version, we could consider the option of another instance. 

Or should we start having another instance with a view to buying for selected users?  

[Alex Koxaras -Relational-]

Hi @Michael Chuong 

No unfortunately you can't. What you can do, is to have another instance for trialing Jira Premium.

If you activate/buy Jira premium on your current instance it will be for all users. But if I may ask, what is the feature(s) that you don't want your users to have? Or you simply don't want to pay the Premium price for all users?

[Alex Koxaras -Relational-]

@Michael Chuong to answer the following question:

The features in premium version will not be applicable to the majority of users.  Only a couple of manager-level users want the extra features.  

But if it is visible to all users and have no operation impact on existing projects with standard version, that is still fine too during the trial period. 

Only on buying the premium version, we could consider the option of another instance. 

Or should we start having another instance with a view to buying for selected users?

As I said earlier, you can't buy the premium for a portion of your users. You either are on a premium plan, or on a standard plan.

If you start another instance with a trial of the premium plan and further down the road you decide that it's good for you, then you should also consider how these two instances will communicate with each other (if of course there is such need).

Take a look at this comparison https://www.atlassian.com/software/jira/pricing

Even if you trial the premium version, the new feature will not have an impact on your current users in my opinion.

[Michael Chuong]

Thanks Alex for your insight.  I have forwarded the information back to the TGG manager and I guess our senior management team will have to think through the benefits from buying the premium.

Can you also ask you this further query that if we are to upgrade existing instance to premium version and say later decide to stop or roll back to standard version after final call, this roll back should not have operational impact? and the new Jira tickets created under premium version should also be operational under standard version on same instance? 

[Michael Chuong]

meaning that there would not be any 'version incompatibility' after roll back?

[Alex Koxaras -Relational-]

@Michael Chuong you will not lose any data on issues, but the additional functionalities that jira premium offers, will be lost. E.g. the following functionalities:

will be lost. So if e.g. you have a jira automation rule which runs across multiple projects, you will not be able now to do that. It will not work. Same thing with roadmaps etc.

There will not be any version incompatibility afterwards.

The only crucial thing that I'm thinking of, is the storage. Standard version offers 250GB of storage, while premium plan offer unlimited. Don't know what will happen if you have used more storage and you want to go back to a smaller plan. For that matter I would probably contact Atlassian directly.