Manage Jira Filter Permissions
Share the saved filter with the intended audience while retaining actual issue-level access controls. Filter visibility and permission to browse matching issues are separate.
Step-by-step guide
Check access and scope
The filter owner or an authorized editor must manage sharing, and users may need an appropriate global permission to share filters.
Identify filter ownership
Open filter management and identify the maintained filter owner.
Review filter scope
Inspect JQL for sensitive or obsolete scope.
- Worked example: A release-review filter can be visible to the release group while security issues remain protected by issue security. A shared filter name should not disclose sensitive customer details itself.
Choose viewers and editors
Choose specific viewers and editors for the use case.
Audit dependent dashboards
Review dashboards or boards that depend on the filter.
Test recipient access
Test the filter using an intended recipient account.
Verify the result
Recipients can open the filter and see only work they are authorized to browse.
Common mistakes
Check the handoff edge case
A broad editor group can change a filter used by many dashboards. Restrict editing to maintainers who understand its consumers.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.