As an admin did you ever lost admin access to a Team Managed project with no way to know?
If a project admin removes your group from the Administrator role in a Team Managed project, you lose access to that project's settings silently. There's no notification, no dashboard showing which projects are affected, and the only workaround is manually editing the URL to reach project settings.
I ran into this repeatedly and first solved it with a Jira Automation rule that queries the API to surface affected projects — if anyone's interested in that approach, happy to share it.
But I wanted something more accessible, so I built a Forge app for it. You select any Jira group (e.g. jira-administrators) and instantly see which Team Managed projects are missing it as Administrator. You can add the group back directly from the app, no URL hacking needed.
It's free, requires no external setup, and runs entirely within your Atlassian site.
Would love feedback from the community, especially if you've hit this gap before.
This was the first real hurdle I had as an admin. It's been a few years but I still don't allow Team Managed spaces because it was such a nightmare.
Like many others, we've prohibited Team Managed spaces, but that's great, see a problem, fix a problem, and something that probably should have been in the App itself from the beginning.
Assume this only affects instance level Jira Administrators? As an org-admin on an enterprise licence I've found I am always able to see all Spaces in any of our individual JIra instances and add myself in whenever an end user has requested support.
Hi @Ignacio Vera, if you're part of a Marketplace App team, we would like to ask you to follow the steps outlined here to get an 'Atlassian Partner' lozenge for your profile!
For additional context, you can also refer to the Atlassian Partners - Rules of Engagement.
Cheers!