How Jira Admins Can Find and Fix Abandoned Items Faster (Without Doing It All Manually)

[#1]

If you manage a Jira Cloud instance, you probably know what this feels like. The system runs smoothly, and teams rely on it every day. Still, behind the scenes, things can slowly start to drift. Maybe there’s a ticket still assigned to someone who left the company six months ago. Or a dashboard owned by a former team lead. Or a saved filter that no one manages anymore, but three different teams still rely on it.

None of these issues will break Jira on its own. But over time, they make it harder to manage, harder to report on, and harder to trust.

This article looks at why this problem keeps happening and what you can do about it today. You’ll also find a faster way to build the internal tools that help you stay on top of things.

Why Inactive User Ownership Becomes a Governance Problem

When someone leaves a company or changes roles, their work leaves traces in Jira. Some of those traces are obvious. Most are not. The most common ones administrators run into:

• Unresolved issues are still assigned to deactivated users.

• Saved filters owned by accounts that no longer exist in an active state.

• Dashboards built by former team leads that other people still rely on daily.

The challenge is not that these problems cause immediate disasters. Instead, the main problem is visibility. Often, admins are unaware of what exists until something fails or someone notices a dashboard has not been updated for months.

Over time, these orphaned items lead to what many admins call configuration drift. This is the gradual build-up of inconsistencies that makes a Jira instance more difficult to understand and update.

What You Can Do in Jira Cloud Right Now

Before jumping to any tooling solution, it is worth understanding what is natively available, because some of this you can do today, without anything extra.

Finding Unresolved Issues Assigned to Inactive Users

In Jira Cloud, you can use JQL to surface issues assigned to inactive accounts. A few useful queries:

resolution = Unresolved AND assignee WAS IN (inactiveUsers())

If you already have a list of specific deactivated accounts (which you can export from your Atlassian Admin console under User Management), you can search more directly:

assignee in ("user1@example.com", "user2@example.com") AND resolution = Unresolved

This gives you a starting point for identifying work that has effectively gone unowned.

Finding Filters Owned by Inactive Users (Jira Cloud)

To get started in Jira Cloud, open Jira Settings, then go to System, select Shared items, and choose Filters. Once there, search by owner. If you know which accounts are inactive, use your Atlassian Admin console to confirm. Then, search by email to find filters owned by those users.

For each filter, you want to ask:

• Is this filter still used by active teams or linked dashboards?

• Does it need to be reassigned to an active owner?

• Is it safe to delete?

Based on your answers, either delete the filter or assign it to a new owner.

Finding Dashboards Owned by Inactive Users (Jira Cloud)

The steps are almost the same. Go to Jira Settings, then System, select Shared items, and choose Dashboards. Search using the email of an inactive user and review each dashboard you find. Some dashboards may be outdated, while others could be important reports that need a new owner right away.

Using the REST API for Bulk Review

If you’re dealing with a long list of inactive users, checking them one by one in the admin UI isn’t practical. Instead, Jira Cloud’s REST API can help

 GET /rest/api/3/filter/search?expand=owner 

endpoint returns filters along with owner details, so you can cross-reference them against your inactive user list and get a bulk view instead of checking accounts individually.

The Real Problem: You’re Working in Pieces

Even with everything mentioned above, the manual approach has a basic flaw. JQL shows you issues. The admin UI shows you filters. Dashboards are on another screen. You end up piecing everything together from different places, running the same searches for each inactive account, and trying to remember it all while deciding what to reassign, archive, or delete.

This process isn’t bad, just incomplete. What admins really need isn’t another search. It’s an audit view, a single report that brings everything together, so you can review without jumping between screens.

How to Build an Audit View with AI Apps Builder for Jira

That’s where AI Apps Builder for Jira can help. AI Apps Builder is a Jira Cloud app that lets you create custom Forge apps just by explaining what you need in simple terms. You describe the tool you want, and the system builds a complete Forge app for you. This includes the user interface, backend logic, permissions, and module setup, all ready to deploy to your Jira Cloud instance.

You don’t need to write any code or submit a development request. Just describe your problem, and the app will generate a working solution for you.

I started with the simple prompt:

Create a dashboard report for Jira admins with three tables: issues assigned to inactive users, dashboards owned by inactive users, and filters owned by inactive users. Each table should show the main details needed to review, reassign, or clean up abandoned Jira items.

Instantly, I got the result - Inactive Ownership Auditor, a custom dashboard gadget that brings all three views together in one place.

With this tool, admins don’t have to switch between JQL, shared filters, and dashboards. They get one structured report. Instead of rebuilding the search every week, they have a reusable audit tool they can use whenever they need it.

What AI Apps Builder Actually Builds for Admins

AI Apps Builder for Jira creates Forge apps, which use Atlassian's official framework for Jira Cloud. These aren't workarounds or browser scripts. They are real Jira Cloud apps that run on Atlassian's own infrastructure and follow all the permissions and security rules that Forge offers.

Three real examples from admins who used it:

Space Security Monitor. Jira gives admins no easy way to spot projects with overly permissive Browse Projects settings. This app surfaces security exposure across all spaces in one view, with critical misconfigurations clearly flagged — no manual project-by-project review needed.

Cost Center License Manager. Jira does not offer built-in tools to link user groups to cost centers, monitor license use by department, or automate monthly cost reports. This app takes care of removing duplicate users, figuring out which product licenses are in use, and sending cost reports by email automatically.

Automated Jira Issue Assignment System. Manual issue assignment is slow, error-prone, and ignores who is actually available. This app replaces it with intelligent automation that factors in team workload and availability to route new issues accurately from the moment they are created.

Each started as a plain-language description of an admin problem. Each became a deployed Forge app.

What Admins Say About AI Apps Builder

Admins who have used AI Apps Builder say it is both fast and practical:

"I love everything about this app. It helped me solve a problem that I have had for years. I was able to solve it in a matter of minutes."

"It's very easy to get started and quickly generate a working Jira gadget without needing to write code. I like how it understands intent from prompts and creates a functional baseline that I can iterate on. It significantly reduces the effort needed to build custom dashboard visualizations."

"Crucial step for app building, thanks team."

The main theme in this feedback is speed and accessibility. Admins who have spent years finding workarounds for Jira's limits now see that simply describing what they need can be the first step to getting it.

Who AI Apps Builder Is For

If any of these situations sound familiar, this will be useful for you.

• You manage a Jira Cloud instance with a growing or long-lived user base.

• You spend meaningful time every week on Jira maintenance and cleanup.

• You have recurring admin problems that you solve manually because no built-in tool covers them.

• You want to build internal governance tools faster without waiting on development resources.

AI Apps Builder for Jira is especially helpful for admins who know what tool they need but do not have the time or resources to build it. If you can explain your problem clearly, the app can create a working starting point for you.

Final Thought

Most Jira admin work is not dramatic. It is maintenance: keeping the system healthy as teams change, configurations build up, and ownership shifts over time.

The inactive ownership problem is a good example of work that is easy to put off because it does not cause immediate failures, but over time, it makes everything harder to manage. Having a dedicated audit tool that you can run regularly, without rebuilding it from scratch each time, is much more practical than doing it manually across multiple screens.

AI Apps Builder for Jira is worth trying if you have admin problems like this: specific, recurring, and fixable with the right internal tool. It is now much easier to build that tool than it was before.