Advanced Filter Manager

Overview

Advanced Filter Manager is a powerful Jira Cloud app that gives you full control over your saved filters. Jira's built-in filter management can feel limited when dealing with a large number of filters across multiple teams and projects. This app provides a centralized view to organize, search, share, tag, and maintain your filters effortlessly.

Key Features & Usage

1. Bulk Operations

Select multiple filters at once to perform mass updates, saving you clicks and time. Through the bulk actions menu, you can bulk-update tags, bulk-share, bulk-remove access, and bulk-change owners across dozens of filters simultaneously.

2. Filter Tagging

Stop relying on awkward naming conventions to group your filters. Add custom tags directly to any filters you have permission to edit to create intuitive categories (e.g., "q3-okrs", "frontend-bugs").

• Add, remove, or create new tags inline on individual filters, or efficiently through bulk operations.
• Easily filter your main dashboard view by one or multiple tags.

3. Sharing & Permissions Management

Quickly view who has access to which filters. Make filters private, or share them broadly with specific Users, Groups, or Project Roles.
Note: This action is executed via bulk operations and strictly respects Jira user permissions (you can only update sharing settings on filters you have permission to edit).

4. Change Ownership

When colleagues move teams or leave the company, their important filters often get stuck or orphaned. Advanced Filter Manager allows you to easily transfer ownership of filters to another team member to ensure continuous maintenance.
Note: This action is executed via bulk operations and strictly respects Jira user permissions.

5. Manage Favorites & Advanced Searching

Beyond bulk changes, the main dashboard provides essential capabilities for everyday filter management:

• Favorites: Individually manage whether a filter is marked as a 'favorite' right from the main list view.
• Advanced Filters: Find exactly what you need by filtering the dashboard based on filter name, owner, tags, or by toggling to only show filters you can edit.

Required Scopes & Data Usage

Because the app modifies structural Jira components, Atlassian Forge requires you to grant specific permissions (scopes) upon installation. We strictly follow the principle of least privilege.

Technical Limitations

To guarantee maximum performance and stability within Atlassian's strictly partitioned Forge ecosystem, we enforce sensible bounds on certain features:

• Filtering by Permission: The app only displays filters that you have permission to view or edit. If a colleague created a totally private filter, it will not appear for you, even if you are a Jira Admin (this is an underlying Jira REST API constraint).
• Tag Limits: A maximum of 15 tags can be assigned per filter, and each tag is limited to 50 characters (alphanumeric, hyphens, and underscores only). This prevents UI clutter and ensures the tag-search engine remains lightning fast.
• Tag Search Limits: When searching by tags, a strict safety cap is placed at a maximum of 500 filter results. This is a hard limit (not paginated) designed to ensure the app complies with Atlassian Forge's strict 25-second backend execution timeouts and to prevent browser memory exhaustion. If you have more than 500 filters with the same tag, only the first 500 accessible ones will be returned.
• Editable Only Filter Limit: When the "Editable only" toggle is enabled, the app scans up to 10,000 filters to identify those you have edit permission on. If your instance has more than 10,000 filters visible to you, results are truncated and an informational banner is displayed: "Showing the first 10,000 editable filters. Use search or tag filters to narrow your results." This primarily affects Jira administrators on very large instances, as regular users typically see far fewer filters. This limit exists because Jira's API does not support filtering by edit permission server-side — the app must check each filter individually, and Atlassian Forge enforces a 25-second execution timeout per request. Normal paginated browsing, search by name or owner, and other features are not affected by this limit.
• Bulk Edit Thresholds: Bulk operations are capped at 1,000 filters per action. Additionally, to respect Jira's strict REST API rate limits and avoid overwhelming your instance, bulk actions are processed in small batches. Wait times for massive bulk edits (e.g., hundreds of filters) may be longer.

Installation

Alternatively, you can install it directly from your Jira instance:

1. Log into your Jira instance over the web.
2. Navigate to Apps > Find new apps.
3. Search for "Advanced Filter Manager".
4. Click Try it free. Accept the required scopes.
5. Once installed, use the top navigation: Apps > Advanced Filter Manager.

Licensing

Advanced Filter Manager is a commercial app available on the Atlassian Marketplace. It provides a full-featured free trial period, after which an active license is required for continuous use. You can easily manage your subscription directly from your Jira administration settings.

Need Help?

Encountering issues, have a question, or want to request a feature? Reach out to our support team and we'll be happy to assist you.