Study guide
9.4 Dashboard Layouts, the Default Dashboard, Sharing & Essential Gadgets
Atlassian Certified Professional - Jira Administration for Cloud ACP-120
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview, Blueprint & Jira Cloud Fundamentals
1.1 ACP-120 Exam Structure, Blueprint & Testing Strategy 1.2 Jira Cloud Architecture, Products & Admin Hierarchy
2 Chapter 2: Organizations, Managed Accounts & Global Access
2.1 Atlassian Organizations, Domain Verification & Managed Accounts 2.2 Atlassian Guard, SAML SSO, SCIM & Authentication Policies 2.3 Site Access, Product Access Tiers & Global Permissions 2.4 User Directory Architecture: Groups vs. Project Roles
3 Chapter 3: Project Permissions & Issue-Level Security Schemes
3.1 Permission Scheme Mechanics & Critical Project Permissions 3.2 Permission Troubleshooting, Additive Permissions & Permission Helper 3.3 Issue Security Schemes, Security Levels & Access Containment
4 Chapter 4: Project Configuration, Types, Versions & Boards
4.1 Company-Managed vs. Team-Managed Project Architecture 4.2 Project Templates, Project Keys & Project Categories 4.3 Project Components, Component Leads & Default Assignees 4.4 Versions, Fix Versions, Release Lifecycles & Project Archiving 4.5 Scrum and Kanban Board Configuration, Board Filters & Columns
5 Chapter 5: Issue Types, Custom Fields, Screens & Schemes
5.1 Standard vs. Sub-task Issue Types & Issue Type Schemes 5.2 Custom Field Types, Global vs. Project Contexts & Options 5.3 Field Configurations, Renderers, Hiding & Required Fields 5.4 Screens, Screen Schemes & Issue Type Screen Schemes
6 Chapter 6: Workflows — Company-Managed and Team-Managed
6.1 Statuses, Status Categories, Direct & All-to-One Global Transitions 6.2 Transition Rules: Conditions vs. Validators 6.3 Post Functions, Execution Order & Resolution Management 6.4 Workflow Schemes, Editing Active Workflows & Status Migration 6.5 Team-Managed Workflows, Statuses & Workflow Rules
7 Chapter 7: Jira Cloud Automation
7.1 Automation Engine, Rule Architecture & Event Triggers 7.2 Automation Conditions, Smart Values & String/Date Expressions 7.3 Branch Rules, Related Issues, Sub-tasks & Parent Epics 7.4 Rule Scopes, Automation Usage, Audit Logs & Error Handling
8 Chapter 8: Notifications, Events, Personal Settings & Mail Handlers
8.1 Jira Events, System Events & Notification Schemes 8.2 Notification Recipients, Custom User Fields & Deduplication 8.3 Team-Managed Notifications, Personal Settings & Troubleshooting Missing Email 8.4 Mail Handlers: Creating Issues and Comments from Email
9 Chapter 9: JQL, Filters, Dashboards & Bulk Operations
9.1 JQL Fundamentals, Clauses, Operators & History (WAS / CHANGED) 9.2 Advanced JQL Functions & Dynamic Date Searches 9.3 Filter Permissions, Shared Filters & Filter Subscriptions 9.4 Dashboard Layouts, the Default Dashboard, Sharing & Essential Gadgets 9.5 Bulk Operations: Edit, Move, Transition, Delete & Watch
10 Chapter 10: System Administration
10.1 Global UI Features: User Defaults, Look and Feel, Announcement Banner & Default Dashboard 10.2 Statuses, Resolutions, Priorities & Sub-tasks: Global Configuration 10.3 Global Settings: Time Tracking, Issue Linking, Attachments & Application Links 10.4 System Backup, Restore & Data Import
9.4 Dashboard Layouts, the Default Dashboard, Sharing & Essential Gadgets
Key Takeaways Explain This Topic AI
Dashboards provide real-time operational visibility through configurable multi-column layouts (1, 2, or 3 columns) populated by dynamic reporting gadgets.
Only Jira admins configure the default dashboard (Settings > System > Default dashboard); it can't be deleted and can be shared only with the organization or the public.
Dashboard sharing permissions mirror filter sharing (Private, Public, Group, Project/Role), but gadget data visibility is strictly gated by underlying issue and filter permissions.
Essential gadgets include Filter Results, Pie Chart, Created vs. Resolved Issues, Two-Dimensional Filter Statistics, and Sprint Burndown.
Wallboard mode transforms dashboards into high-visibility rotating monitors for team rooms, requiring performance tuning of gadget refresh intervals.
Last updated: September 2026
9.4 Dashboard Layouts, the Default Dashboard, Sharing & Essential Gadgets
Quick Summary: Dashboards provide real-time visual summaries of project health, operational workload, and SLA compliance across Jira Cloud. A dashboard consists of a configurable multi-column page populated by specialized reporting gadgets . While users can design personal dashboards, Jira admins govern the default dashboard that welcomes new users. Administrators must understand the three-tier permission model separating dashboard access, saved filter access, and underlying project data permissions, as well as the optimal configuration of core gadgets (Pie Chart, Filter Results, Created vs. Resolved, Two-Dimensional Filter Statistics) and Wallboard displays.
Dashboard Architecture & Layout Topologies
Navigating to Dashboards in the top navigation bar allows users to view their starred favorite dashboards or create new custom reporting spaces. Every dashboard in Jira Cloud is built upon a flexible grid layout system. +--------------------------------------------------------------------------+
- | DASHBOARD LAYOUT TOPOLOGIES |
- +--------------------------------------------------------------------------+
- | [1] Single Column (100%): |
- | Ideal for wide data tables, Filter Results with many fields, |
- | and complex Two-Dimensional Statistics matrices. |
- | |
- | [2] Two Columns - Balanced (50% / 50%): |
- | Standard operational layout; pairs charts alongside issue lists. |
- | |
- | [3] Two Columns - Asymmetric (67% / 33%): |
- | Primary working column for tables paired with a narrow side rail |
- | for metric counters, Assigned to Me, and Quick Links. |
- | |
- | [4] Three Columns (33% / 33% / 33%): |
- | Best for executive KPI summaries, pie charts, and simple metrics. |
- | Poor fit for wide text tables or multi-column filter results. |
- +--------------------------------------------------------------------------+
- The Default Dashboard vs. Custom Dashboards
The default dashboard (older documentation calls it the System dashboard ):
It's what users see when they first log in, until they choose their own dashboards.
Only Jira admins configure it, in Settings > System > User interface > Default dashboard . There they can add gadgets, Edit layout , and view it as a wallboard.
It can't be deleted .
Admins can share it only with My organization (signed-in users) or Public (anonymous visitors too), not with specific groups, projects, or people. Choose My organization to turn off anonymous access.
If you add a gadget that some users can't use (for example, an admin-only gadget), those users simply don't see it.
Custom dashboards:
Users with app access create their own ( Dashboards > Create dashboard ) and can share them if they hold Share dashboards and filters .
Users can star dashboards to add them to their favorites.
Dashboard Sharing & The Three-Tier Security Model
A frequent source of confusion and support escalations in enterprise Jira administration is the Three-Tier Dashboard Security Model : +--------------------------------------------------------------------------+
- | THREE-TIER DASHBOARD PERMISSION CASCADE |
- +--------------------------------------------------------------------------+
- | |
- | [TIER 1: DASHBOARD CONTAINER PERMISSION] |
- | Can the user view the dashboard layout itself? |
- | Configured via: Dashboard Details > Edit permissions (Group, Project) |
- | | |
- | v [PASS] |
- | [TIER 2: SAVED FILTER PERMISSION] |
- | Can the user access the saved filter powering the specific gadget? |
- | Configured via: Filter Details > Edit permissions |
- | *If Private -> FAILS with 'Filter Not Found / No Permission' error* |
- | | |
- | v [PASS] |
- | [TIER 3: ISSUE-LEVEL & PROJECT SECURITY PERMISSION] |
- | Does the user possess 'Browse Projects' and meet Issue Security Levels? |
- | Configured via: Permission Schemes & Issue Security Schemes |
- | *If unauthorized -> Gadget displays '0 issues' (Silent redaction)* |
- | |
- +--------------------------------------------------------------------------+
- Diagnosing Dashboard Visibility Failures
Symptom 1: User cannot open the dashboard at all.
Root Cause: The dashboard container permissions (Tier 1) are set to Private or restricted to a group/project the user does not belong to.
Symptom 2: User opens the dashboard, but a gadget displays an error box stating: "The filter for this gadget could not be found or you do not have permission to view it."
Root Cause: The dashboard container is shared, but the underlying saved filter (Tier 2) powering that gadget is Private or has not been shared with the user.
Symptom 3: User opens the dashboard, the gadget loads with empty charts or "0 issues found", while colleagues see 50 issues.
Root Cause: Both the dashboard and the filter are properly shared, but the user lacks the Browse Projects project permission or fails the Issue Security Scheme level (Tier 3) on the returned issues. Jira silently suppresses unauthorized records to prevent information disclosure.
Essential Jira Cloud Reporting Gadgets
Selecting the right gadget for specific reporting requirements is heavily tested on the ACP-120 exam.
Gadget Name Primary Visualization Configuration Parameters Best Administrative Use Case
Filter Results Tabular list of issues Saved filter, number of results (1–50), display columns Project triage queues, unassigned bug lists, release verification checklists.
Pie Chart Segmented circular chart Project or Saved filter, Statistic type (Assignee, Status, Priority, Component, Custom Field) Visualizing workload distribution across assignees or breakdown of issues by status category.
Created vs. Resolved Issues Dual-line chart or bar graph Project/Filter, Period (Daily, Weekly, Monthly), Days previously (e.g., 30, 90), Cumulative? (Yes/No), Display versions Tracking engineering velocity and identifying whether technical debt is growing (created > resolved) or burning down.
Two-Dimensional Filter Statistics Cross-tabulation matrix table Saved filter, X-axis statistic, Y-axis statistic, Number of results Risk triage (Priority vs. Severity), capacity planning (Assignee vs. Status), component health (Component vs. Priority).
Assigned to Me Filter results table Number of results Personal task cockpit; dynamically evaluates currentUser() for the viewer.
Sprint Burndown Line chart Scrum Board, Sprint (Active or Next), Quick filters Tracking active sprint completion trajectory against the ideal burndown guideline.
The Power of Two-Dimensional Filter Statistics
The Two-Dimensional Filter Statistics gadget is one of Jira's most analytical administrative tools. By plotting two independent field dimensions against each other, managers can instantly spot operational bottlenecks: +-------------------------------------------------------------------------+
- | TWO-DIMENSIONAL STATISTICS: ASSIGNEE vs. PRIORITY |
- +-------------------------------------------------------------------------+
- | Assignee | Blocker | Critical | Major | Minor | Total |
- | ------------- | ------- | -------- | ----- | ----- | ----- |
- | Alex Chen | 2 | 4 | 8 | 1 | 15 |
- | Sam Rivera | 0 | 1 | 3 | 6 | 10 |
- | Taylor Swift | 5 | 6 | 2 | 0 | 13 <-- Overloaded |
- | Unassigned | 3 | 2 | 0 | 0 | 5 <-- At Risk |
- | Total | 10 | 13 | 13 | 7 | 43 |
- +-------------------------------------------------------------------------+
- Wallboard Display Mode & Performance Optimization
A Wallboard is a specialized display mode that transforms a Jira dashboard into a high-contrast, full-screen visual information radiator designed for display monitors in team rooms, Network Operations Centers (NOC), or trading floors.
Activating Wallboard Mode
From a dashboard's tools or more-actions menu, choose View as wallboard . The default dashboard supports this too ( Tools > View as Wallboard ), and several dashboards can be combined into a wallboard slideshow :
In Wallboard mode, gadgets expand into high-contrast dark cards optimized for distance viewing.
If multiple gadgets exist, the Wallboard can be configured to rotate automatically through gadgets in a continuous slideshow.
Performance & Maintenance Best Practices
Dashboards and Wallboards query the Jira database frequently. Poorly designed dashboards can significantly degrade overall site performance:
Avoid Aggressive Auto-Refresh Intervals:
Most gadgets support an Auto refresh setting (e.g., Every 15 minutes ).
Never set high-volume dashboards to refresh every 1 or 2 minutes, especially if displayed on multiple unattended TV wallboards across the enterprise. A 15-minute refresh interval is the standard enterprise best practice.
Optimize Underlying Saved Filters:
Gadget performance is directly dictated by JQL efficiency. Avoid using unconstrained historical searches ( WAS , CHANGED ) or unindexed wildcards in gadget filters.
Always bound gadget filters by active projects: project in (PROJ1, PROJ2) AND resolution is EMPTY .
Prune Orphaned Dashboards:
Jira admins can search dashboards by owner, change the owner , or delete them from the admin Dashboards page (Settings > System, under shared items). Do this when an owner leaves.