How to Create Rich Filter in Jira 2026 Easily Setup Smart Rich Filter in Jira

From your Jira sidebar, open Apps, then Explore more apps, and search for Rich Filters for Jira Dashboards, built by Appfire. The listing shows its rating, install count, and a Cloud Fortified trust badge, along with an overview video demonstrating dynamic dashboards and gadgets — worth a quick watch before installing so you know what the finished result looks like. Click Add to install it into your site; once added, it shows up under Your apps in the sidebar as Rich Filters.

Open Rich Filters from your app list and click Create rich filter. The dialog asks for a Name for the filter and a Jira filter to base it on — this base filter is what narrows down which issues the rich filter starts working with, so pick or search for an existing saved filter that already scopes to the right project, board, or issue type before building anything smarter on top of it.

Inside the new rich filter, go to Static filters or Dynamic filters and click Create smart clause. Give the clause a name and color, then write the condition in the JQL field — as you type, Jira suggests matching values, for example autocompleting status names like Delivery, Discovery, or Done as you type `status = `. Each clause becomes a selectable filter option on the dashboard, so name them for what a viewer would actually want to click, not just their JQL syntax.

Any existing clause can be reopened through Edit smart clause, where you can rewrite the JQL entirely — for instance swapping a simple status condition for something more specific like tracking a chart's date range or a custom field. This is normal maintenance rather than a sign something broke; rich filters are meant to be refined as the questions your team is asking evolve.

From any Jira dashboard, click Add gadget and search for the Rich Filters gadget, then select the rich filter you built. Viewers see your named smart clauses as clickable filter options rather than a JQL box, and the gadget's results update instantly as they switch between clauses — this is the payoff for building clauses with clear, human-readable names in the earlier step.

Revisit the rich filter periodically as sprints, statuses, or team structure change, since a clause built around a status or field that no longer exists will just return empty results without any obvious warning. Treating the filter as a living part of your dashboard, rather than something you set up once and forget, is what keeps the reporting actually reflecting current project data.