Are there any plans for a more flexible licensing model for JIRA? We have some teams who want access to plugins, but those plugins aren't required by everyone.
The need to buy licenses that match the overall JIRA license numbers is meaning the business case for those plugins is not working out, as the cost per head of people actually intending to use the plugin is too high.
by deafult, each plugin follows tool users number license so you need to buy plugin respecting your tool users number. This approach is in place for all third-part plugins that use atlassian licensing system (90%).
Hope this helps,
Atlassian allows Vendor to define its own license management (https://developer.atlassian.com/display/MARKET/License+Validation+Rules)
A license is invalid if its maximum number of users property is less than that of the application license:
Application is licensed for a fixed limit; plugin license has a fixed limit that is lower
Suggested Error Message:
Invalid license: Your ADD_ON_NAME is only licensed for LIMIT_VALUE users. Your ATLASSIAN_APPLICATION installation requires a license for LIMIT users. Please get a ADD_ON_NAME license for LIMIT_VALUE users and try again.
So, each vendor could define license user limit.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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