9.3 Filter Permissions, Shared Filters & Filter Subscriptions

9.3 Filter Permissions, Shared Filters & Filter Subscriptions

Quick Summary: In Jira Cloud, a saved filter is a reusable JQL query stored in the database with a unique numeric ID. Saved filters represent the architectural foundation for agile boards, dashboard gadgets, cross-project reports, and automation rules. If a filter's permissions are misconfigured, downstream dashboards break with "Filter Not Found" errors. Jira Administrators must master filter visibility scopes, the global permissions governing who can share objects, the security mechanics of personal vs. group email subscriptions, and the administrative lifecycle for transferring filter ownership when staff depart.

---

Saved Filters Architecture & Dependencies

When a user executes a search in Filters > Advanced issue search, the search results are transient. Clicking Save filter (or Save as) prompts the user for a Filter Name and optional description, persisting the query as a global entity with a unique ID (e.g., filter=10450).

+--------------------------------------------------------------------------+
|                       SAVED FILTER DEPENDENCY GRAPH                      |
+--------------------------------------------------------------------------+
|                                                                          |
|                     +-----------------------+                            |
|                     |   SAVED JQL FILTER    |                            |
|                     |     (Filter ID)       |                            |
|                     +-----------------------+                            |
|                           |     |     |                                  |
|             +-------------+     |     +-------------+                    |
|             v                   v                   v                    |
|    +-----------------+  +-----------------+  +-----------------+         |
|    |  Agile Boards   |  | Dashboard Gadget|  | Email Scheduled |         |
|    | (Scrum/Kanban)  |  |  (Pie, Filter)  |  |  Subscription   |         |
|    +-----------------+  +-----------------+  +-----------------+         |
|                                                                          |
+--------------------------------------------------------------------------+

The Relationship Between Filters and Downstream Assets

• Agile Boards: Every Scrum and Kanban board in Jira Software is powered by an underlying board filter. If the creator of the filter restricts its visibility, team members lose access to the entire board.
• Dashboard Gadgets: Gadgets such as Filter Results, Pie Chart, and Two-Dimensional Filter Statistics reference a saved filter ID rather than embedded JQL.
• Email Subscriptions: Scheduled email alerts evaluate the filter's JQL on a cron cadence and dispatch matching issues to subscribers.
• Editing JQL vs. Filter Definition: If a user modifies the JQL text of a saved filter in the search interface, Jira displays the filter name with an asterisk (*FilterName). The changes do not take effect on downstream boards or dashboards until the user explicitly clicks Save.

---

Filter Sharing Scopes & Permissions

Filter owners (and editors) set Viewers and Editors in the filter's details. Atlassian lists these sharing targets:

A filter can have several sharing entries at once (for example, a project role and two groups). Owners can also grant edit access to users, groups, or projects so others can maintain the JQL.

Sharing a filter never shares issues. Each viewer only sees the issues their own permissions allow. Two people opening the same shared filter can get different results.

Default access for new filters comes from the admin's user default settings (Private or Public). Changing that default doesn't share any existing filter.

---

Prerequisites for Sharing: Global Permissions

The person sharing needs Share dashboards and filters. The people viewing a shared filter don't.

---

Filter Subscriptions: Personal vs. Group

A Filter Subscription is an automated service in Jira that executes a saved filter on a scheduled basis and emails the resulting issue list as an HTML or text digest to subscribers.

+--------------------------------------------------------------------------+
|                    PERSONAL VS. GROUP FILTER SUBSCRIPTIONS               |
+--------------------------------------------------------------------------+
| Parameter            | Personal Subscription     | Group Subscription     |
| -------------------- | ------------------------- | ---------------------- |
| Target Audience      | The individual user       | An entire Jira Group   |
| Required Permission  | View permission on filter | 'Manage group filter   |
|                      |                           |  subscriptions' global |
| Execution Context    | Subscriber's permissions  | Individual recipient's |
|                      |                           |  permissions respected |
| Email Suppression    | Optional (can email 0)    | Optional (can email 0) |
| Scheduling Engine    | Daily, Weekly, Cron       | Daily, Weekly, Cron    |
+--------------------------------------------------------------------------+

1. Personal Subscriptions

Any user who has permission to view a saved filter can create a personal subscription for themselves (Filter details > Subscriptions > Add subscription):

• Schedule Options: Daily (at a chosen time), Days per week, Days per month, or Advanced Cron expressions.
• Zero-Issue Notifications: Users can check the box "Email this filter, even if there are no issues found". This is a powerful administrative auditing tool. For an escalation filter (priority = Blocker AND status = Open), an engineer leaves this unchecked so they are only alerted when blockers arise. For a compliance filter (resolution is EMPTY AND duedate < now()), a manager might leave it checked to receive daily confirmation that zero tickets are overdue.

2. Group Subscriptions

Group subscriptions email a filter's results to every member of a Jira group:

• Mandatory privilege: the person creating it needs the Manage group filter subscriptions global permission.
• Group membership: you can only choose a group you are a member of as the recipient.
• Results are specific to each recipient. Jira runs the filter for every member separately, respecting their project permissions and issue security. A member who can't browse Project X gets an email without Project X's issues.
• currentUser() is evaluated as the recipient. A filter like assignee = currentUser() AND resolution is EMPTY sent to a group gives each person their own open work. (This doesn't apply when the "recipient" is a distribution-list email address rather than a Jira group.)

Troubleshooting Filter Subscriptions

---

Filter Governance & Managing Orphaned Filters

A major operational challenge in enterprise Jira administration occurs when an employee departs the company. When their Atlassian account is deactivated:

1. The saved filters they owned remain in the system.
2. If the filter was shared, other users can still view it, but no non-admin user can edit the JQL or update filter sharing.
3. If a team lead needs to modify a board filter owned by a departed user, they cannot do so without administrative intervention.

Administrative Transfer of Ownership

Jira admins can manage and reassign shared filters in Settings > System > Filters:

• Search Shared Filters: Administrators can search by filter name or filter owner (including inactive accounts).
• Change Owner: Clicking the action menu (...) next to any filter allows the administrator to select Change owner and transfer ownership to an active project lead or manager.
• Delete Filter: Deleting a filter breaks any board or dashboard gadget that uses it, so check with the owner and consumers first.