How to Create a Dashboard in Jira with Filters That Show What Matters

Jira dashboards display real-time project information through collections of gadgets showing issue statistics, sprint progress, and team workload. Without filtered data, these dashboards overwhelm users with irrelevant information from multiple projects and teams. Filters refine dashboard content to show only the issues, metrics, and trends relevant to specific roles or objectives.

Organizations that know how to create a dashboard in Jira with filters gain targeted visibility into project health. According to project management research from Atlassian, dashboards facilitate informed decision-making by providing timely, accurate access to project data and real-time updates, enabling project managers to streamline their decision-making and make well-informed choices that drive project success.

Build JQL Filters That Target Specific Data

Jira Query Language provides the foundation for filtered dashboards. JQL queries specify exactly which issues appear in dashboard gadgets by combining fields, operators, and values into structured queries. These saved filters become reusable across multiple gadgets and team members.

Basic JQL structure follows field-operator-value patterns. The query “project = Marketing AND status = In Progress” returns all active Marketing project issues. The query “assignee = currentUser() AND priority = High” returns high-priority items assigned to whoever is viewing the dashboard. These queries filter thousands of issues down to relevant subsets.

Operators determine filter logic. Equals (=) matches exact values. Not equals (!=) excludes specific items. Greater than (>) and less than (<) compare numerical or date values. IN operator matches multiple values simultaneously: “priority IN (High, Critical)” finds both urgency levels. IS EMPTY identifies missing field values, which are useful for finding unassigned work.

Functions add dynamic capabilities. The currentUser() function automatically filters by viewer identity, making dashboards personalized without creating separate filters for each user. The openSprints() function shows issues in active sprints. The startOfWeek() function enables time-based filtering that updates automatically. These functions create filters that remain relevant as data changes.

Create Dashboard Layouts for Different Audiences

Dashboard effectiveness depends on matching the selection of gadgets to audience needs. Executive dashboards require high-level metrics. Team dashboards need detailed work breakdowns. Individual contributor dashboards focus on personal assignments. Different layouts serve different purposes without duplicating effort.

Executive dashboards display project health through summarized metrics. The Issue Statistics gadget shows total bug counts and resolution rates. The Created vs. Resolved gadget tracks whether teams close issues faster than they arrive. The Pie Chart gadget breaks down work by priority or issue type. These gadgets use broad filters covering entire product areas or multiple projects.

Team dashboards combine workload visibility with sprint tracking. The Sprint Health gadget displays current sprint progress and completion forecasts. The Filter Results gadget lists specific issues the team currently handles. The Average Age gadget highlights issues that have been pending updates for too long. These gadgets apply team-specific filters: “project = Platform AND assignee IN (alice, bob, carol)” or “sprint IN openSprints() AND team = Backend”.

Individual contributor dashboards emphasize personal accountability. According to Jira dashboard research from HevoData, organizations can use Jira dashboards as real-time visibility hubs by including gadgets like Sprint Health, Burndown Charts, and Blocker Filters that surface sprint progress, highlight at-risk issues, and show blockers upfront.

The Assigned to Me gadget shows the current workload. The Activity Stream gadget tracks recent changes to watched issues. The Time Tracking gadget monitors hours logged against estimates. These dashboards use “assignee = currentUser()” filters that automatically personalize for each viewer.

Configure Gadgets to Answer Specific Questions

Each dashboard gadget addresses specific project management questions. Selecting appropriate gadgets requires understanding which questions stakeholders ask and which gadget types answer them most effectively.

Filter Results gadget answers “what work is currently in this state?” It displays issue lists matching any saved filter. Configuration options control visible columns: key summary, status, assignee, and priority. This gadget is well-suited to detailed work reviews, where users need to see individual issue information and may click through to issue details.

The Issue Statistics gadget answers the question: “How many issues exist in each category?” It shows counts grouped by any field: status, priority, assignee, component. Bar chart visualization makes comparative volumes clear at a glance. This gadget supports capacity planning questions such as “how many critical bugs remain?” or “which team member carries the most assigned work?”

Created vs. Resolved gadget answers, “Are we keeping up with incoming work?” It plots two lines over time: issue creation rate and resolution rate. When the resolution line stays above the creation line, the backlog shrinks. When lines cross, the backlog grows. This trend analysis identifies whether teams need additional resources or scope reduction.

The Control Chart gadget answers the question: “How long do issues take to resolve?” It displays cycle-time distributions with statistical bounds. Short cycle times indicate efficient workflows. Long cycle times or wide distributions signal process inconsistencies. This gadget supports continuous improvement discussions by quantifying flow efficiency.

Maintain Dashboard Relevance Through Regular Updates

Dashboards lose value when underlying filters become outdated. Team structures change. Project priorities shift. Sprint schedules evolve. Regular filter maintenance ensures dashboards continue showing relevant information rather than historical artifacts.

Quarterly filter reviews align dashboards with the current organizational structure. Review each filter’s JQL to verify it references active projects, current team members, and relevant priorities. Remove filters for completed initiatives. Add filters for new product areas or teams. Update project lists when reorganizations occur.

Sprint-based filters need updates at iteration boundaries. Filters using “sprint = 23” become outdated when sprint 24 starts. Replacing explicit sprint numbers with “sprint IN openSprints()” creates self-updating filters. A similar approach works for version-based filters: “fixVersion IN unreleasedVersions()” always shows future work without manual updates.

Dashboard sharing permissions require ongoing management. Private dashboards serve individual needs. Shared dashboards need appropriate access controls. Team dashboards should be editable by team leads and viewable by all team members. Executive dashboards might be view-only for most users but editable by specific analysts. Permission reviews prevent unauthorized modifications while ensuring necessary access.

Filtered Jira dashboards transform raw issue data into actionable visibility. JQL queries define precise data subsets. Layout choices match information presentation to audience needs. Gadget selection answers specific management questions. 

Regular maintenance keeps dashboards up to date as organizations evolve. Teams implementing these practices create dashboards that inform decisions rather than just display data.