Overnight (Jun 17, 2026) one of my instances that is enrolled in developer canary program now have “Marketplace apps” under Jira Admin Settings redirected to admin.atlassian.com directly instead of requiring the admin users to click “Take me there”.
Instances that are not in canary program don’t seem to have been affected yet as of writing.
I also noticed that the canary program itself is only visible in the same side bar of /plugins/servlet/upm and it’s also no longer visible anywhere in Jira admin settings.
The direct URL workaround does work — navigating straight to /jira/settings/apps/{appId}/{envId} opens the `jira:adminPage` fine, so the page itself is still there and rendering correctly.
The actual problem is that there’s no longer any way to reach it from the Jira UI. “Manage apps” → “Marketplace apps” now just redirects to admin.atlassian.com/.../user-connected-apps/installed\, which doesn’t list Forge admin pages at all. So unless you already know the deep link, there’s no discoverable entry point to a `jira:adminPage` anymore.
Certainly worrysome that this is gone.
Fyi, there is another way to reach the adminPage: Via the Configure-action on Connected apps. You may have to set useAsConfig: true in your manifest to enable this, see docu.
FYI – This was just accepted as a bug report. However, it is currently marked Low Priority. Please consider voting for a bug fix and adding a comment to explain the impact to the relevant Atlassians.
We’ve been hit by this as well. Our Forge apps rely on jira:adminPage for configuration, and since UPM was removed from canary instances, our admins have completely lost the ability to navigate to those pages through the Jira UI. The only option right now is sharing direct URLs manually, which is obviously not a sustainable workflow.
What’s particularly frustrating is that a change of this magnitude — effectively breaking the entire discoverability of Forge admin pages — was rolled out without proper testing or even a migration path. There was no deprecation notice, no alternative UI entry point provided, and no documentation update. This is a production-facing surface that app developers and their customers depend on daily.
A few things we’d really like clarity on:
Is there a timeline for restoring navigation to jira:adminPage from within Jira’s UI?
Will the new admin experience atadmin.atlassian.com be updated to surface Forge admin pages alongside connected apps?
Is there a recommended workaround beyond manually constructing deep links (/jira/settings/apps/{appId}/{envId})?
We understand that UPM deprecation is part of a larger platform shift, but breaking existing Forge extension points without a ready replacement is really not acceptable. Would appreciate an official response on the expected timeline and the planned resolution.
Would still be good to know what the plan is for this view, as having this primary action guiding users away from the settings is still not optimal.. If any Atlassian is readying this at some point, would be interesting to learn what the long term vision for this is…
