Now my question:
Reason of my question:
I hope somebody have idea, how this works or give me the correct documentation link.
There are two workflows that can happen, depending on if this is an evaluation license or non-evaluation license.
Evaluation license: after the expiration date, the plugin will be expired and not function anymore. UPM will offer updates to newer versions because either way (with the current or newer versions), they won't work with the expired licenses.
Non-evaluation license: these licenses don't *expire*, but rather, they *maintenance-expire* meaning that the plugin can continue being used as is, but the user cannot receive support nor update to newer versions after the maintenance expiration date. UPM 2 will notify the user that there is an available update for the plugin but that it is incompatible with the installed license, and will recommend that the user acquire a new license first.
If the user ends up with a version that is incompatible with their license, they can always uninstall it and then install an older (compatible) version.
can I set real expiration (not only maintenence expiration) for my plugin somewhere - maybe in atlassian-plugin.xml? That means - plugin will fully work 12 months and then only some functionality will be available till user buy renewal license. Is this possible?
No - following the Marketplace model in place, purchased plugin licenses are always perpetual; twelve months after the purchase date, the plugin will still function properly but the user will no longer be able to update to newer versions or receive support. All Marketplace plugins should follow this model.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.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