Hi @LukasGotter,
Thanks for raising this. We understand your frustration and the challenges you face. We are taking an iterative approach to solve this, with the first milestone focusing on decoupling versions from permissions. This will address the main reasons for creating major app versions: scope, egress, and remote changes. It will reduce installations of older versions and the number of outdated major versions requiring support.
While this iteration is a positive step, it will not fully resolve app update issues, as customers will still need to approve any permission or pricing changes. Future milestones will streamline release notes and improve how permission approval requests reach admins to boost approval rates. We will also let app developers define features, each consisting of scopes and/or permissions, allowing them to specify which features are optional or mandatory.
For future milestones we are exploring how to reduce the rate of changes that require admin consent such as exploring pathways for scope changes that may not require admin consent, e.g. storage and other equivalent scope changes that may be platform-driven. We may allow customers to pre-consent to certain groups of scopes, enabling automatic rollout of changes requiring scopes from a pre-approved list. Alternatively, we may consider allowing customers to pre-consent to changes that do not cause loss of Runs on Atlassian eligibility for apps that already meet the criteria.
Cheers,
Agi