-
Type:
Bug
-
Resolution: Fixed
-
Priority:
High
-
Component/s: Forge - App UI Web
-
Major
-
Pollinator tests
Issue Summary:
Forge App with jira:fullPage Forge module is not accessible on Jira-only Cloud instances(Cloud instances which only have Jira site and not confluence).
Steps to Reproduce
- Make sure that Cloud instance is only having Jira site only.
- Deploy and Install a Forge app with jira:fullPage module app on a Cloud site with only Jira app. Confluence App should not be there in site.
- Access app with url mentioned in doc Navigation - Full Page Module. Also monitor network tab in browser dev console.
https://<your-site>.atlassian.net/forge-apps/a/<app-id>/e/<forge-environment-id>/r/<route-prefix>/<app-route>
- We find error in graphql response with statusCode 404 and classification as ProductMissingException.
{ "errors": [ { "message": "TCS did not contain requested product: confluence", "locations": [], "extensions": { "product": "confluence", "cloudId": "<cloud-id", "errorSource": "GRAPHQL_GATEWAY", "statusCode": 404, "agg": { "severity": "NORMAL", "ugcPiiSafe": true }, "classification": "ProductMissingException" } } ],
- We don't observe this error when Cloud site has Jira and confluence.
Expected Results
- Forge Jira fullPage module should work for site not having Confluence application.
Actual Results
- In Browser dev panel for graphql request we find response with statusCode 404 and classification as ProductMissingException.
{ "errors": [ { "message": "TCS did not contain requested product: confluence", "locations": [], "extensions": { "product": "confluence", "cloudId": "<cloud-id", "errorSource": "GRAPHQL_GATEWAY", "statusCode": 404, "agg": { "severity": "NORMAL", "ugcPiiSafe": true }, "classification": "ProductMissingException" } } ],
- The below exception is thrown in console of browser dev panel.
Error: GraphQL error: TCS did not contain requested product: confluence at new t (main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:26:516520) at main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:26:538133 at main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:26:544469 at Set.forEach (<anonymous>) at main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:26:544445 at Map.forEach (<anonymous>) at e.broadcastQueries (main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:26:544124) at main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:26:546342 at Object.next (main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:91:7076) at g (main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:91:4900) at w (main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:91:5406) at e.value (main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:91:5959) at main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:26:531778 at Set.forEach (<anonymous>) at Object.next (main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:26:531740) at g (main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:91:4900) at w (main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:91:5406) at e.value (main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:91:5959) at main.706656e48008f7138e6b.bundle.js?706656e48008f7138e6b:142:93432
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available