This is what we have now: "For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for add-ons." Reference: https://marketplace.atlassian.com/plugins/com.radiantminds.roadmaps-jira -> Picing tab
I think you're missing the background of what an "application" is in this context. JIRA 7 split JIRA into three products - Core, Software and Service Desk. They're being marketed as separate products, but what they *really* are is: JIRA Core JIRA Software = JIRA Core with the Software Application installed JIRA Service Desk = JIRA Core with the Service Desk Application installed Applications are the new feature for JIRA 7 - they're JIRA Applications that run within Core. Not separately. An incorrect, but simple and useful way to think of them is "A different type of add-on". Service Desk and Software used to be add-ons, but now they're Applications. But still JIRA applications. I can't think of a single reason why a Portfolio customer would go elsewhere just because it changes from an add-on to an application. The move would have some benefits in terms of cost and flexibility for some users, and absolutely zero downsides.
...and you will continue to pay as a "core features" so for all users. the only plugin (provided by atlassian) that has a different license type is "service desk" but they have created a lot of bloking permission and features to create something similar of other "pay per use" system. A lot of users complain about plugin costs, because plugin are related to product license tier. If you want to add a small features to jira, you will have to pay it for all users...Service desk is different because has a different target (people outside system) and usually product like this one (zendesk ..etc) has a license not related o end users (This is my opnion as a user)
Atlassian price it that way, not us - we're end-users, like you.
If you're only having 3-4 people using Portfolio from a 100 user base, that's telling me that it's not something you really need. So I'd skip it. I totally agree with you - for a couple of people who might benefit, it's not worth it as the rest of you won't!
Only three to four people using Portfolio sounds about right for a 100 person user base. It will only be used by a couple of Project Managers and Product Owners to create road maps and to show progress to the exec through reports, so the cost is pretty prohibitive.
Feeling sad about being forced to license for all our users for several products that I would love to use, but once you add three or four of these items, suddenly you go from 1K to 6K and that puts these products out of range and we have to choose which one's are the highest priority.
What a shame.
You can get most of the information you need from: https://www.atlassian.com/licensing/jira-portfolio
Here is the answer that Nic already gave to you: https://www.atlassian.com/licensing/jira-portfolio#serverlicenses-5
This is obviously what most companies are requesting from Portfolio, i don't know if it still works like that but it looks that most of their market would choose it as an option if only we could have less than 50 licenses in a 200+ users environment. Trying to match it with the number of core licenses is just against its own logic.
A read only posibility would be logical also, but having every user with rights to create and modify roadmaps just doesn't make sense.
Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events