Tips & Best Practices

Practical advice for building better dashboards, faster.

Data Sources

Use Saved Filters for shared dashboards. If multiple people use the same dashboard, build your Jira filter once (save it in Jira), then reference it as the data source. When the filter changes, all gadgets update automatically - no need to edit each gadget.

Use JQL for precision. sprint in openSprints() AND project = TEAM is more reliable than selecting the project and trusting it always shows the right sprint. Test your JQL in Jira's Issue Navigator before using it in a gadget.

Set the Dynamic Filter Controller's base JQL tightly. The more focused the base scope, the faster the dashboard loads. Use project = X AND issuetype in (Story, Bug, Task) rather than just project = X if you don't need sub-tasks or epics in most views.

Custom Charts

Use Templates to start fast. Apply a template first, then customize. It is faster than building from scratch. See Templates.

Keep segment count under 10. Charts with more than 10 segments become hard to read. Use Custom JQL to group rare values into an "Other" segment.

Use Cumulative Total on line charts for running totals. When you want to show "total issues resolved this quarter", use the Cumulative Total calculation instead of week-by-week counts.

Add a Description tab note. For stakeholder dashboards, use the Description tab to explain what the chart shows in plain language - no Jira jargon.

Issue List

Use Smart Labels to surface risk. Add a red "Overdue" label (duedate < now() AND resolution is EMPTY) and an orange "Due Soon" label (duedate <= 7d AND resolution is EMPTY). These appear on every row without filtering - leadership sees risk at a glance.

Export after filtering. The CSV and PDF exports reflect the current filtered state. Apply Quick Filters first to export exactly the subset you need - e.g., only critical unassigned bugs.

Use AND logic for focused lists, OR logic for catch-alls. AND: "Show me bugs that are also unassigned" (narrower). OR: "Show me anything that's either overdue or unassigned" (broader catch-all for triage).

Time in Status

Start with Average Time to find bottlenecks. Sort descending. The top row is your slowest stage. See Display Settings & Export for interpretation tips.

Use Business Decimal Days for SLA reporting. Calendar time includes nights and weekends. If your SLA is "resolve P1 within 2 business days", always use a Business format. Set up your Work Schedule first in the gadget settings.

Cycle Time vs Lead Time - know the difference. Cycle Time starts when work actively began. Lead Time starts from creation. Report Lead Time to stakeholders. Use Cycle Time to evaluate your team's actual process speed.

Pivot Table

Start with Row Heatmap for workload analysis. Assignee × Status with Row Heatmap immediately shows who has the most "In Progress" or "In Review" work - no reading required.

Make values clickable for drill-through. Enable "Make Values Clickable" so any cell opens the matching Jira issue list. This is the fastest way to go from summary to detail.

Use date field formatting for trend pivots. When using Created or Resolved as a column field, set the format to "Month" or "Quarter" for cleaner grouping in management reports.

Cumulative Flow Diagram

Use "Latest sprint auto" on permanent team dashboards. With Latest Sprint Auto selected, the CFD always shows the current sprint - no one needs to update it after each sprint transition. See Date Ranges & Scoping.

Watch for widening bands, not total height. A widening "In Review" band means work is piling up in review faster than it is leaving. The total height rising is normal (scope growing). A single band widening is the bottleneck signal.

Use 1-week interval for releases, 1-day for active sprints. Daily intervals on a 90-day release chart create noise. Switch to weekly for longer time windows.

WIP Aging Charts

Use in every daily standup. Open the chart at the start of standup. Any dot past the threshold line gets a discussion: "What's blocking this? Can it be cleared today?" No sorting or filtering needed.

Set the 85th percentile line as your SLE. "85% of our work completes within X days" - this is a data-driven commitment. Track whether the line moves over time to measure process improvement. See Reference Lines & Scale.

Exclude weekends if your SLA is in business days. Enable "Exclude Weekends" so items sitting over weekends don't falsely trigger your threshold line.

Performance

Keep queries under 10,000 issues. Add date filters or project scoping to JQL for large Jira instances. created >= -90d is often enough to keep queries fast without losing useful data.

Use auto-refresh sparingly. Auto-refresh every 10 minutes is useful on live dashboards shown in team areas. Turn it off for dashboards used in weekly meetings - manual refresh is enough and avoids performance overhead.

Import / Export

Back up configurations before big changes. Use the Import/Export tab on any gadget to export its JSON configuration. Save to a shared document or Confluence page before making major changes - this is your restore point.

Duplicate gadgets instantly. Export a configured gadget → add a new gadget of the same type → import the JSON. A complete configuration is copied in seconds with no manual re-setup.