If 'Core' is licensed for 10000 users, but I have only 50 that need Portfolio, will I still be recommended to "Purchase the license tier that matches the number of users you have licensed for your host application"?
It seems like the new licensing model allows for more flexible deployment, in that I can allow access to Portfolio only from the Group who requires it.
Is this the case? Will I have a 10000 user 'Core' license, with another 10000 user license for 'Service Desk' also supporting my 50 Portfolio users and 500 Agile users?
A Marketplace FAQ update or other 'authoritative' source is much appreciated!
(Info from Partners is highly regarded (thanks, Nic))
Update: Licensing model is changed a lot in JIRA 7. Please see @Nic Brough [Adaptavist]'s comments and examples in below.
Yes it needs to match JIRA User licensing, that means if you have 10000 user JIRA license you should also purchase Portfolio for 10.000 users. Please check FAQ under Pricing tab of Portfolio page : https://marketplace.atlassian.com/plugins/com.radiantminds.roadmaps-JIRA
Only add-on that has different pricing model is Service Desk. It is based on agents not number of your JIRA users.
Great question! We have the same situation (only have about 50 real users of Portfolio out of 2000) - this license change is good but what is the point if we still have to purchase Portfolio for the same number of 'Core' users? It should be intelligent enough to limit active users at any time to no more than 50.
Ok, I've had my understanding confirmed many times now. Applications are licenced on a user basis, but add-ons need to match the licence numbers for the application they are linked to. Portfolio is an add-on for JIRA Core, so it will need to be licenced at the highest tier you have Core users for. (It is a logical candidate to become another application, but I have no idea if or when this could happen) So... The simple example is JIRA Core 2000 users. You need 2000 Portfolio users too. The more complex example is when you have one of the two Applications installed. Let's go with: JIRA Core users: 50 JIRA Software users: 100 This lets a total of 150 different users use JIRA. 100 of them can use everything, 50 of them can only use Core, they won't get access to Software functions like boards. As Portfolio is an add-on, then you will need to licence it for 100 users in this case, as that's the higher number of users. (p.s. William, I work for a partner, if that helps)
It still confuses me, because how can you have 100 software users and only 50 core? If you buy a 100 users licence for JIRA software you automatically get a 100 core users licence. And if you buy an additional licence of 50 core users you in fact have 150 core users. Then you would have to compare 150 core against 100 software users, and the highest is 150, because all of them could use Portfolio.
No. You're not understanding that the licences are for separate things. If you buy 100 Core users, you have 100 Core users, that's fine. You can NOT buy "another 50 Core users", because the next tier is 250. Now, imagine I've got 100 Core. I now get 50 Software users. Software licences give you Core + Software. So adding that to my current installation gives me 100 Core + 50 Software (and the 50 Software users can also use Core). Finally, my highest licence tier there is 100, so Portfolio needs to be licenced for 100.
Now we're on the same page :) And as you said earlier - Portfolio is a logical candidate to become an application. As long as it's licenced as add-on we can't jusitfy the cost in our organization. I think most companies have fewer potential Portfolio users than Core users.
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs