Let's imagine the following scenario: a company has 100 Confluence users, a plugin with perpetual license is bought, then after one year the company increases the users to 200. What happens to the license of that plugin? Will the first 100 users be able to use it and the new ones not?
Thank you!
Hi @Timóteo Daniel Rodrigues de Azevedo
In my experience most vendors will need that you pay for the new higher user count of the main product (even if they use the Add-on/App only with a part of your users). This is the case because most of the plugin functionality is just an extension to the functions of the main product and will be availably (in theory) for all possible users. And this is the number they base their pay on.
In my opinion this isn't optimal because if only one sup-group of a company needs a specific tool it can be cheaper (thorugh more complex) if they have their own application index with a 10 user license of the main application and the necessary apps. But as far as my knowledge reaches this is the way it is. And I as an atlassian consultant hat some opportunites to research this topic ;)
With kind regards
Mario
Hi Mario,
Thank you for your reply. I'm aware about Atlassian license policies regarding Add-ons, which, between us, are bit bollocks. :)
When you say "most vendors will need that you pay", how can they force me to do that? If I bought a perpetual license for x number of users, my guess is that this plugin will work for x number of users. If not, my question is: what happen to the plugin if I increase the number of Jira users without purchasing an upgrade for the plugin license?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Timóteo Daniel Rodrigues de Azevedo
the license won't be valid anymore (they can determine the application license= after upgrade and they just disable the app functionality in this case.
Regards,
Mario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In case of 'paid-via-vendor' App, it is decided by the App vendor. In case of 'paid-via-atlassian' the decision is with Atlassian.
One of our App is 'paid-via-vendor' and the number of users of our App can be separately configured. In this case it doesn't matter if the user has upgraded or downgraded Jira license.
For the 'paid-via-atlassian' case, this is what I found in Atlassian's documentation:
The price to upgrade from a lower to higher license tier for Server apps is calculated based on Atlassian's formula, as seen here for Jira Software. We automatically calculate the appropriate price based on the license upgrade formula when you add the license upgrade to your shopping cart.
Read the full answer in FAQ here: https://www.atlassian.com/licensing/marketplace#licensingandpricing-6
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What App allows this licensing on the numer of app-users? Never come about one so thsi is an opportunity for me to learn new stuff :).
Regards
Mario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mario CarabelliI am not sure if I am allowed to post our App here. But because you have asked, here it is - https://marketplace.atlassian.com/apps/30899/rmsis-requirements-management-for-jira?hosting=datacenter&tab=overview
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.