When JIRA Enterprise licensees were migrated to the new licensing model, they got a grandfathered equivalent 'unlimited' license. This means that JIRA reports unlimited for user count, which means plugins using that for license size validation also report unlimited.
In this scenario, where the actual users are somewhat less, say 400, and would naturally fit into the 101-500 user bracket, and would then allow plugin licensing tier to be more appropriate. Does Atlassian support 'right/down sizing' of JIRA licenses to minimise ongoing costs of plugins? Making plugins ignore reported license count seems... wrong.
As a side note, its also unclear how the new Marketplace license management deals with grandfathered licenses (not in the marketplace FAQ).
The plugin license and the host application license types and user counts need to match (more info).
We are working on a license import mechanism that can be used by vendors to tell us about their existing licensed customers, so that they will get the renewal pricing when it comes time to renew. Stay tuned to the marketplace mailing list for more details on this feature.
Sorry bring back up this old thread, but I would just like to confirm the answer to the original post
"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"
So, is this saying, for example that the Grandfathered unlimited JIRA user licenese (100+) needs to be paired with an add on license that has a users propery of 10,000+? Even if the actual number of users in the instance is significantly lower? like in the 200 - 300 user range?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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