-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Forge - Automations
-
Severity 3 - Minor
Issue Summary:
The capabilitySet property is missing from the license object when accessed via useProductContext inside a Forge Automation Action. The same app correctly returns capabilitySet in other module contexts such as Issue Panel. This prevents apps from performing edition/plan-based license gating within automation actions.
Steps to Reproduce
1. Create a Forge app with both a jira:issuePanel module and a jira:automationAction module
2. In the Issue Panel module, fetch useProductContext and display.
3. In the Automation Action module (config UI or action function), call useProductContext and log context.license.capabilitySet
4. Trigger the automation rule containing the Forge action
Expected Results
useProductContext.license.capabilitySet should return the edition/plan value.
Actual Results
The license object does not contain capabilitySet
"license": { "active": true, "type": "commercial", "supportEntitlementNumber": null, "trialEndDate": null, "subscriptionEndDate": null, "isEvaluation": null, "billingPeriod": "MONTHLY", "ccpEntitlementId": null, "ccpEntitlementSlug": null, "__typename": "AppInstallationLicense" }
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available