Hello Atlassian Community! π
I'm excited to announce that I just released a new app on the Atlassian Marketplace: Advanced Filter Manager.
Anyone who has administered a growing Jira Cloud instance knows the pain of "filter creep."
Because Jira gives teams the freedom to create filters for their boards and dashboards, shared filters accumulate rapidly. As teams evolve and project scopes shift, managing this footprint manually becomes an administrative bottleneck.
Without native folder structures or categorization systems, administrators and power users often resort to manual workarounds like hacking together strict naming conventions (e.g., prefixing everything with [Marketing] or Q4-) just to keep things organized.
When you need to update permissions or hand over ownership of dozens of filters during team transitions, you are forced into a cycle of manual updates: Click, edit, save, repeat.
I wanted to build an utility that makes this process fast, clean, and secure without compromising Jira's permission model.
Built on Atlassian Forge, the Advanced Filter Manager provides a single interface to organize, update, and search shared filters at scale.
Hereβs what the app does in practice:
The Problem: Jira does not have a native tag or folder system to categorize filters, forcing teams to rely on fragile naming conventions.
The Solution: The app allows you to instantly apply custom tags to multiple filters at once. You can search and filter your shared filters using these tags, making it simple to keep your workspace clean and organized.
Bulk Owner Changes: Easily reassign ownership of multiple filters at once when team members change roles or depart.
Bulk Permission Management: Add, remove, or modify sharing permissions (by space, group or user) for dozens of filters in a single batch operation instead of editing them one-by-one.
Strict Security Guardrails: The app respects Jira's native security model. Users can only modify filters they own or have explicit edit rights to.
Because the app is built 100% on Atlassian Forge:
It runs entirely on Atlassian's secure infrastructure.
No external servers are involved.
No filter content or user data is sent outside of your Atlassian instance.
We designed this tool to save Jira Admins and Project Leads hours of manual, repetitive maintenance while keeping your instance structured and secure.
π Get the Advanced Filter Manager on the Atlassian Marketplace
π Documentation
How does your organization currently handle shared filter cleanup or categorization? Do you enforce naming conventions, or do you have another strategy?
Let me know your thoughts, questions, or feature requests ideas in the comments below!
Regards
Florian Bonniec
1 comment