JIRA Dashboards and Gadgets
A JIRA Dashboard is a customizable home screen that displays project data through visual widgets called Gadgets. Dashboards turn raw JIRA data into meaningful snapshots that help managers, Scrum Masters, and stakeholders monitor progress without digging through boards or running manual searches. Every user gets a personal dashboard by default, and administrators can create shared dashboards for entire teams or organizations.
What Is a JIRA Dashboard?
A dashboard is a configurable screen made up of one or more gadgets arranged in columns. Each gadget connects to a filter or project and displays data in a visual format — a pie chart, a bar chart, a table, a countdown, or a list. JIRA ships with a default system dashboard, but every user and team should create custom dashboards suited to their specific monitoring needs.
Analogy: A JIRA Dashboard works like a car instrument panel. The speedometer, fuel gauge, and temperature gauge each show one critical metric at a glance. A driver does not open the engine hood to check speed — the dashboard shows it instantly. JIRA dashboards do the same for project health.
Dashboard vs Board
| Aspect | Dashboard | Board |
|---|---|---|
| Purpose | Status summary and management visibility | Day-to-day task tracking and movement |
| Audience | Managers, Product Owners, stakeholders | Development team doing the active work |
| Content | Charts, counts, tables, and lists | Issue cards in status columns |
| Action type | Read-only monitoring | Interactive — drag cards, update status |
| Scope | Can span multiple projects | Scoped to one project and one sprint |
| Data source | Filters and project data | Active sprint and workflow statuses |
Creating a Dashboard
Step-by-Step Process
| Step | Action |
|---|---|
| 1 | Click Dashboards in the top navigation bar |
| 2 | Click Create Dashboard |
| 3 | Enter a name (e.g., "MBA Project — PM Dashboard") |
| 4 | Set sharing permissions (Private, Project, Group, or All users) |
| 5 | Click Create — an empty dashboard opens |
| 6 | Click Add Gadget to start adding widgets |
| 7 | Search for a gadget, click Add, and configure it |
| 8 | Drag gadgets to arrange them in the preferred column layout |
JIRA Gadgets: The Dashboard Building Blocks
Gadgets are the individual widgets that populate a dashboard. JIRA provides many built-in gadgets, and marketplace plugins add more. Here is a complete reference of the most important gadgets.
| Gadget Name | Display Type | What It Shows | Best Used By |
|---|---|---|---|
| Filter Results | Table / List | Issues returned by a saved JQL filter | All users |
| Pie Chart | Pie chart | Issues grouped by a field (Priority, Status, Assignee, etc.) | Managers, Product Owners |
| Two Dimensional Filter Statistics | Table | Cross-tabulation of two fields (e.g., Status vs Assignee) | Scrum Masters, PMs |
| Burndown Chart | Line chart | Remaining story points over sprint days | Scrum Masters |
| Velocity Chart | Bar chart | Committed vs completed points across sprints | Product Owners |
| Assigned to Me | List | Issues currently assigned to the logged-in user | Developers |
| Activity Stream | Feed | Real-time updates on issue changes across projects | All users |
| Issue Statistics | Bar chart / Table | Count of issues grouped by any field | Managers |
| Created vs Resolved | Line chart | New issues created vs resolved over time — shows backlog growth or shrinkage | Product Owners, PMs |
| Average Age Chart | Bar chart | Average age (in days) of open issues by field value | Managers |
| Recently Created Issues | List | Latest issues added to a project or filter | Project Leads |
| Sprint Health Gadget | Summary block | Sprint completion percentage, days remaining, completed points | Scrum Masters |
| Text | Free text / HTML | Team announcements, notes, or instructions on the dashboard | Admins, PMs |
| Days Remaining in Sprint | Countdown | Number of working days remaining in the current sprint | Dev Team |
Configuring a Gadget
Each gadget has configurable fields that control what data it shows. Click the pencil icon on any gadget to open its configuration panel.
| Field | Setting | Result |
|---|---|---|
| Filter | Open Bugs in MBA Project | Limits data to bugs in the Mobile Banking App project |
| Statistic Type | Assignee | Slices the pie by who each bug is assigned to |
| Refresh Rate | Every 15 minutes | Updates the chart automatically without manual refresh |
Dashboard Layout Options
JIRA offers different column layouts for dashboards. Choose a layout based on how many gadgets the dashboard needs and the type of data displayed.
| Layout | Column Structure | Best For |
|---|---|---|
| Single Column | 1 wide column | Large charts or single-focus dashboards |
| Two Columns (50/50) | Two equal columns | Balanced mix of gadgets |
| Two Columns (70/30) | One wide + one narrow column | Main chart left, supplementary list right |
| Three Columns (33/33/33) | Three equal columns | Data-dense management dashboards |
| Three Columns (25/50/25) | Narrow + wide + narrow | Central chart with context on each side |
Sample Dashboard Designs for Different Roles
Scrum Master Dashboard
| Gadget | Configuration | Purpose |
|---|---|---|
| Sprint Health Gadget | Current sprint, MBA project | Quick sprint completion status |
| Burndown Chart | Active sprint, MBA project | Is the team on track to finish on time? |
| Two Dimensional Filter Statistics | Sprint issues: Status vs Assignee | See individual workloads and status distribution |
| Filter Results | Filter: Flagged issues in open sprint | List of all blocked or flagged items needing attention |
Product Manager Dashboard
| Gadget | Configuration | Purpose |
|---|---|---|
| Velocity Chart | MBA project, last 6 sprints | Track team capacity and delivery trends |
| Created vs Resolved | MBA project, last 30 days | Is backlog growing or shrinking? |
| Pie Chart | Open bugs by Priority | Risk assessment — how many critical bugs are open? |
| Issue Statistics | Issues by Epic, MBA project | Progress across all features |
| Filter Results | Filter: Overdue issues in MBA | List of issues past their due date |
Developer Personal Dashboard
| Gadget | Configuration | Purpose |
|---|---|---|
| Assigned to Me | All open issues | My full personal workload at a glance |
| Activity Stream | Issues I'm watching | Stay informed on related issues |
| Days Remaining in Sprint | Current sprint | Time pressure awareness |
Sharing and Managing Dashboards
| Action | How to Do It | Effect |
|---|---|---|
| Set as Default | Dashboard menu → Set as my default dashboard | This dashboard opens when JIRA launches |
| Share with Team | Dashboard Settings → Edit → Add share permission | Team members see it in their Dashboards list |
| Favorite | Click the star icon on the dashboard | Appears in Dashboards → Starred for quick access |
| Copy Dashboard | Dashboard menu → Copy | Creates a duplicate with all gadgets — useful for templates |
| Set as System Default | Admin → System → Default Dashboard | All users see this dashboard on first login (Admin only) |
Summary
JIRA Dashboards transform JIRA data into visual management snapshots that serve every role in the team. Gadgets provide the individual widgets — charts, lists, counters, and feeds — that populate each dashboard. Different roles need different dashboards: Scrum Masters want sprint health and burndown data; Product Managers want velocity and epic progress; developers want their personal task list. Creating role-specific dashboards improves decision-making speed and reduces the time spent in status meetings. Dashboards rely on well-built filters and proper user permissions to show accurate data — which leads directly into understanding how JIRA Permissions and Roles govern who can see and do what inside the system.