-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Forge - Jira permission extensions
-
Minor
-
Unit testing, Integration testing
Issue Summary
When a Forge app declares a jira:globalPermission module with defaultGrants: all, the default permission grants are intermittently not applied during a fresh installation.
The global permission entry is created and appears under Jira administration → Global permissions, but no groups are assigned to it. As a result, users may be unable to access app features that are gated behind hasGlobalPermission.
This behaviour has been observed intermittently for some sites: the same app configuration may apply the grants correctly on one fresh installation but fail on another.
Steps to Reproduce
Step 1: Create a Forge app with a jira:globalPermission module using defaultGrants: all:
modules:
jira:globalPermission:
- key: my-global-permission
name: Access My App
anonymousAllowed: false
defaultGrants:
- all
Step 2: Deploy the app.
forge deploy
Step 3: Install the app on a Jira Cloud site where the app has not previously been installed.
forge install --product jira --site <site-url>
Step 4: Go to Jira settings → System → Global permissions.
Step 5: Locate the global permission created by the app.
Expected Results
The global permission should be created and automatically granted according to the defaultGrants: all configuration.
Users covered by the default grants should be able to access app features that depend on this global permission.
Actual Results
The global permission is created, but no groups are assigned to it. Users cannot access app features that depend on this permission until a Jira administrator manually adds the relevant groups.
No error is shown during app deployment or installation.
Workaround
A Jira administrator can manually add the required groups to the app's global permission:
Jira settings → System → Global permissions → [App permission] → Add
This restores access for affected users.