For our app we have a single jira:globalPage module that exposes an entry in the Apps/“Your apps” section of the sidebar. It’s been brought to my attention that for admin users, this entry’s “More actions” menu (…) includes an “App settings” item that, when clicked, takes the user to our app’s only jira:adminPage module that is not marked with ‘useAsConfig’ or ‘useAsGetStarted’.
Is this behavior configurable? I can’t find any documentation for it. In our case it would make a lot more sense for the “App settings” item to send the user to the jira:adminPage that has ‘useAsConfig’ set to true. If changing the target is not possible, we’d like to remove this “App settings” item from the jira:globalPage entry entirely.
@ray_rarey The “App Settings” entry in the “More actions” (•••) menu is automatically created by Jira for any Forge app that includes a jira:globalPage module. You don’t set it up in your manifest; it shows up automatically once your app is installed.
If you want a dedicated settings page, the usual method is:
- Define a second jira:globalPage module in your manifest with a label like “Settings” and a unique key (e.g., settings-page).
- Route to it from your main page using @forge/bridge navigation, or let users find it through the global app menu.
The auto-generated “App Settings” link usually directs to your main jira:globalPage module. If you want it to direct somewhere else, you would need to set up your app so that the primary module is a landing page with tabs or routing.
Hope that helps; let me know if you’re looking to do something more specific with the settings flow.