We’re seeing inconsistent behavior with jira:globalPermission configured as:
anonymousAllowed: false
defaultGrants:
- all
A fresh staging installation receives default group grants, while the production permission has no groups assigned despite the same configuration.
We’ve filed ECOHELP-178255 for investigation. Is anyone else observing similar behavior, particularly in production or following a Connect-to-Forge migration?
I’d check whether the production install predates the global permission module, or was adopted from a Connect app. That would explain it.
The manifest reference says defaultGrants is the group “granted this permissions when the add-on is first installed”. It adds that “existing permission configuration won’t be overwritten during add-on upgrades or re-installations”. An older install keeps its saved config. That holds even when it is empty.
The Connect path matters too. A migrated module keeps its Connect-style key, per the permission migration guide, so production inherits whatever grants the Connect permission had. Some Connect installs started with none, see JRACLOUD-81768, fixed in 2024.
I haven’t reproduced this. If production really is a fresh install with the same manifest, the docs don’t cover it and ECOHELP is the right place. A Jira admin can grant the permission to groups in global permissions meanwhile.
Hmm, I wonder if this is related to when the permission was originally created.
I’m not entirely sure how Forge handles defaultGrants internally, but could it be applying those grants only when the permission is first registered, rather than reconciling them on every deployment?
That might explain why a fresh staging install behaves differently from production, even with the exact same manifest.
One thing I’d be curious about: was the production permission already present before defaultGrants was added or changed?
If so, maybe this isn’t really a staging vs production difference, but a fresh install vs existing installation issue. Worth checking before assuming the manifest is being interpreted differently.
The confirmed bug affects fresh installations, even with a single jira:globalPermission module configured with defaultGrants: all. The permission is created, but its default group grants are intermittently missing. This goes beyond existing installations retaining their saved permission configuration.
For us, the impact is severe. This worked when our app was built on Connect; we started encountering this failure with new installations after moving to Forge. When the default grant is missing, the app does not appear under the Apps section and cannot be launched at all. A customer can complete installation successfully and still have no way to open the app.
That makes jira:globalPermission unreliable for its core purpose. While this bug persists, a module that can intermittently prevent app launch after a clean install is effectively unusable for delivering a reliable installation experience. The risk extends to every Marketplace partner relying on this module to gate app access, not only us.
A Jira administrator can manually add the missing groups as a workaround, but requiring customers to diagnose and repair permissions immediately after installation is not an acceptable long-term solution.
Could Atlassian please treat ECO-1916 as a critical priority and reassess its current Low priority / Minor severity classification?@dmorrow@AdamMoore \ The app-launch-blocking impact warrants urgent engineering attention. Please confirm the priority review and share a target timeline for a platform fix. Reliable access immediately after installation is essential for customers and for Marketplace partners migrating from Connect to Forge.
Thanks for the update, @ajay. I got this one wrong for your case. ECO-1916 shows it intermittently on sites where the app was never installed, so neither install age nor the Connect migration path explains it. The manifest reference note that “existing permission configuration won’t be overwritten during add-on upgrades or re-installations” still holds for upgrades, but it isn’t the cause here.
For anyone else who lands here, I’d watch and vote on ECO-1916. The workaround it gives is for a Jira admin to add the groups under Jira settings > System > Global permissions > your app’s permission > Add.