Hi everyone,
I’m in the process of migrating an existing Atlassian Connect app into a modern React monorepo, and I’ve run into an issue specifically with the configurePage
module that I haven’t been able to resolve.
Issue Description
When I click the “Configure” button for the app from Jira’s Manage Apps section, a blank page opens, and no network request is made to the configured admin page URL. There’s no error in the console, no failed network request, and the iframe doesn’t seem to load at all.
However, if I manually navigate to the same URL in a new tab, the page loads and renders correctly — which suggests the route and frontend setup are working fine.
What Works
- The
viewIssuePanel
is loading correctly inside Jira issues. - The admin config page (
/jira/index.html?view=admin-config&cloud=1
) loads perfectly when accessed directly in the browser. - I also tested a minimal new app with a basic
atlassian-connect.json
usinghelloWorld
for theconfigurePage
, and that works as expected via the “Configure” button.
Context
- App hosted via:
ngrok
during development - Frontend routing: React-based routing with support for
/jira/index.html?view=admin-config
- App descriptor config:
"configurePage": {
"url": "/jira/index.html?view=admin-config&cloud=1",
"name": {
"value": "My App Configuration"
},
"key": "app-config-page"
}
- Scopes used:
"read"
,"write"
,"delete"
What I’ve Checked
- Confirmed that routing and component mounting work fine for this view when accessed directly.
- No errors in the browser console or failed requests in the network tab when clicking “Configure”.
- Verified that other modules (like
viewIssuePanel
) are functioning correctly in the same app context. - Compared app descriptor and permissions with a working helloWorld-based app.
Question
Has anyone experienced something similar where the configurePage
doesn’t load from the Manage Apps section, and no request is even triggered?
I’m wondering if there might be:
- Additional validation Jira does before attempting to load the iframe
- Something in the scopes or descriptor causing the issue silently
- A potential routing or CSP-related issue specific to this module
Any insight or pointers on how to troubleshoot this further would be greatly appreciated.
Thanks!