Best practices for building Dashboards in Plane: 5 examples
Five Plane dashboard examples for engineering leads, PMs, executives, support, and release owners, with the widgets, setup, and mistakes to avoid.
Five Plane dashboard examples for engineering leads, PMs, executives, support, and release owners, with the widgets, setup, and mistakes to avoid.

Engineering, product, and leadership often review the same projects but ask different questions, so one dashboard rarely serves all three. Here are five Plane dashboards, one per role, with the widgets, the setup, and what happens in the review. Each one follows the same few practices, listed below, and the section after the examples covers the setup mistakes that throw dashboard numbers off.
Plane dashboards support these reporting needs through configurable project sources, widgets, and filters. The five examples ahead show how teams can organize their reporting around distinct roles, examine the work behind the numbers, and use those findings in their regular reviews.
The best practices behind every example
The five dashboards serve different roles, and they share a handful of habits that keep them useful from one review to the next:
- Start from the one question the dashboard's audience brings to the review, and leave out any widget that doesn't help answer it.
- Keep the source projects broad at the dashboard level and narrow individual widgets with widget-level filters, so a filter meant for one widget doesn't skew the others.
- Pair each count or chart with a work items table, which gives the review a path from a number to the person who owns the work.
- Before acting on a number, open the work items behind it and check what's actually there.
- Write the scope into each widget's title so anyone reading the dashboard knows what a number covers.
Five dashboard examples by role in Plane
Plane Dashboards bring data from one or more projects into a workspace-level reporting view. Teams can combine charts, number widgets, progress indicators, and work item tables. With filters that narrow each widget to the question it answers.
The following five examples show how different roles can use these capabilities to review engineering execution, project delivery, portfolio risks, incoming requests, and release readiness.
Dashboard | Built for | The question it answers | Plan for the full build |
Engineering execution | Engineering lead | Which blockers and slipping commitments need attention this week? | Business |
Project delivery | Project or product manager | Does the launch date still hold, and what's putting it at risk? | Business |
Portfolio oversight | Executive or portfolio lead | Which project needs a leadership decision, and why? | Pro (Business for the table) |
Request management | Support or Intake owner | Where are requests piling up, and how fast are we deciding? | Business |
Release readiness | Release owner | What could stop us from shipping on the target date? | Business |
1. Engineering lead dashboard
Question: Which blockers and slipping commitments need attention this week?
An engineering lead overseeing multiple projects needs visibility into dependencies, upcoming deadlines, and progress within active cycles. A dashboard combining these signals can highlight potential delivery risks and help the lead investigate the work requiring attention.
Setup in Plane
Select the engineering projects under the lead's responsibility, such as API, Web App, and Platform, as the dashboard's data sources. Use widget-level filters to focus exception metrics on unfinished work while retaining the broader project scope for other reporting needs.
Recommended widgets
Plane widget | Configuration | What it shows |
Number | Blocked work items, filtered to unfinished state groups | Work items with recorded Blocked by dependencies |
Number | Due this week, filtered to unfinished state groups | Unfinished work items with due dates in the current week |
Basic bar | X-axis: Project; Y-axis: Blocked work items; unfinished-state filter | Distribution of recorded blocking dependencies across projects |
Cycle progress bar | Select a project and its active cycle | Cycle completion, state distribution, blockers, and scope changes |
Work items table | Filter for overdue, unfinished work; display assignees, priorities, and due dates | Individual commitments requiring follow-up |
Open Workspace → Dashboards → Engineering dashboard.
Show a dashboard covering multiple engineering projects (for example, API and Web App), with the following widgets visible:
- Number: Blocked work items
- Number: Work items due this week
- Basic bar: Blocked work items by project
- Cycle progress bar for one active cycle
- Work items table showing outstanding items, assignees, priorities, and due dates
Make sure the dashboard shows realistic delivery blockers and overdue or upcoming commitments.
The Blocked work items metric counts work items with a recorded Blocked by relationship. The linked dependency must be examined to determine whether it remains unresolved and how it affects delivery. For other exceptions, PQL conditions such as isOverdue() and hasNoAssignee() help.
Plan availability: Number and Basic bar widgets are available on Pro. Cycle progress bar and Work items table require Business.
What happens during the engineering review?
Ahead of a weekly delivery meeting, an engineering lead reviews the API and Web App projects. The dashboard shows several work items with recorded blocking dependencies in API. In dashboard view mode, the lead selects the API bar to open the matching work items with the relevant filters applied.
One work item, implementing a token refresh endpoint, has a Blocked by dependency on an authentication update owned by the Platform team. After opening the linked work item, the lead confirms that the Platform change remains unfinished and that Web App sign-in validation depends on the endpoint.
The lead can now coordinate with the Platform owner to prioritize the authentication update or adjust the sequence of dependent work. The cycle progress bar provides context on remaining work and scope changes, while the overdue-work table identifies other commitments that may need attention before the next review.
2. Project manager dashboard
Question: Does the launch date still hold, and what's putting it at risk?
A project manager coordinating a product launch needs to understand how larger deliverables are progressing against their planned dates. An Epic may have several completed sub-items while critical validation work remains unfinished, putting the delivery commitment at risk.
Setup in Plane
- Select the launch project or related contributing projects as dashboard sources. Keep completed and unfinished work within the reporting scope, then configure the Work item type progress widget for Epics or other parent work item types.
- It shows each parent's direct sub-item completion, while module-level charts reveal how work is distributed across states. Apply narrower filters to deadline and exception widgets.
Recommended widgets
Plane widget | Configuration | What it shows |
Work item type progress | Select Epic or another parent work item type; use Work item count as the metric | Completion and state distribution of each parent's direct sub-items |
Basic or stacked bar | X-axis: Module; Y-axis: Work item count; stack by State group for the stacked model | Work distribution across modules, with state breakdowns in the stacked model |
Number | Due this week, filtered to unfinished state groups | Unfinished work items with due dates in the current week |
Work items table | Filter for unfinished, high-priority work; show state, assignee, and due date | Individual commitments requiring attention |
Open Workspace → Dashboards → Project delivery dashboard.
Show a dashboard for a delivery project with:
- Work item type progress showing multiple Epics or larger deliverables
- Bar or stacked bar showing work items by module and state
- Number: Outstanding work items due this week
- Work items table showing overdue or high-priority commitments
The dashboard should clearly show deliverable progress, unfinished work, and commitments requiring attention.
Plan availability: Number and Basic bar widgets are available on Pro. Work item type progress, Stacked bar, and Work items table require Business.
What happens during the project review?
A project manager is preparing for a product launch. The Work item type progress widget shows that the Self-serve onboarding Epic still has unfinished direct sub-items. The Module breakdown reveals remaining work in Onboarding, while the work items table identifies two high-priority checks, invitation email validation and account recovery testing, with due dates close to the launch milestone.
After reviewing the outstanding work with its owners, the project manager determines that the checks cannot be completed within the existing timeline. The team agrees to revise the delivery commitment. Where project milestones and updates are enabled, the project manager can adjust the milestone's target date and post a status update in the project's Overview to communicate the revised plan.
3. Executive dashboard
Question: Which project needs a leadership decision, and why?
Executives overseeing multiple projects need visibility into delivery risks that may require decisions beyond individual teams. Outstanding dependencies and overdue high-priority work can highlight areas worth investigating, particularly when several projects compete for shared resources.
Setup in Plane
Select the active projects included in the portfolio review. Configure widgets to compare recorded blockers across projects and identify overdue, high-priority work. Keep the reporting scope consistent, with widget-level filters narrowing each metric to the relevant exceptions.
Recommended widgets
Plane widget | Configuration | What it shows |
Basic bar | X-axis: Project; Y-axis: Blocked work items; filter to unfinished state groups | Projects with recorded blocking dependencies |
Number | Work item count; filter by High/Urgent priority, due dates before the review date, and unfinished state groups | Overdue, high-priority work across selected projects |
Work items table | Apply the overdue, high-priority filters; display project, assignees, state, priority, and due date | Specific work requiring leadership review and its ownership |
Open Workspace → Dashboards → Portfolio overview dashboard.
Show a cross-project dashboard with:
- Basic bar: Blocked work items by project
- Number: High-priority overdue work items
- Work items table showing critical outstanding items, their projects, and assignees
Use multiple projects with realistic differences in blockers and overdue work. The screen should make it easy to identify which project needs leadership attention.
Plan availability: Basic bar and Number widgets are available on Pro. Work items table requires Business.
What happens during the leadership review?
An executive is reviewing the Billing, Identity, and Mobile projects. The dashboard shows several recorded blockers in Billing alongside overdue, high-priority work. Selecting the Billing bar in dashboard view mode opens the matching work items, allowing the executive to examine the dependencies behind the count.
One affected item concerns final invoice validation, which depends on a security review assigned to a shared specialist. The project lead explains that the specialist is currently supporting another initiative, leaving the Billing team unable to complete its planned validation.
With that context, leadership can decide whether to temporarily prioritize the Billing review, allocate additional specialist capacity, or adjust competing priorities. The dashboard identifies the work requiring investigation, while the project lead supplies the delivery impact and resource context needed for the decision.
For formal project-health reporting, Plane's Projects tab in Analytics provides On track, At risk, and Off track classifications on Pro. Only workspace admins can open workspace Analytics, so a dashboard is often the easier way to give executives a recurring view.
4. Support/Intake dashboard
Question: Where are requests piling up, and how fast are we deciding?
Teams managing product feedback, support requests, or internal IT demand need visibility into incoming requests and how long they remain undecided. Plane's dedicated Intake widgets help teams monitor request sources, ageing queues, decision outcomes, and processing times.
Setup in Plane
Select the projects using Intake as dashboard sources. Add the dedicated Intake widgets to track pending, snoozed, and decided requests. These widgets use predefined metrics with limited configuration options. For example, Intake breakdown has fixed metrics, while Intake accepted vs declined supports date grouping and chart-style changes without widget-level filters.
Recommended widgets
Plane widget | What it shows |
Intake breakdown | Request volumes from the app, email, and forms, alongside accepted and rejected totals and average decision time |
Intake items ageing | Pending and snoozed requests grouped into fixed 0 to 2, 3 to 7, and 7+ day bands |
Intake accepted vs declined | Accepted and declined decisions over time, including duplicates in declined totals |
Average time to accept and decline | Average days between request arrival and decision, excluding pending and snoozed requests |
Open Workspace → Dashboards → Intake dashboard.
Show a dashboard using these four Intake widgets:
- Intake breakdown
- Intake items ageing
- Intake accepted vs declined
- Average time to accept and decline
Make sure request sources, ageing bands, accepted/declined counts, and decision times are visible. Use sample data showing pending requests alongside completed triage decisions.
Plan availability: All four dedicated Intake dashboard widgets require Business. Email and public form submissions are also Business features, while in-app Intake is available on all plans.
What happens during the Intake review?
At the start of the week, a support team reviews its request queue. The ageing widget shows several requests waiting for seven or more days, although the average decision time for recently processed requests remains low.
This difference warrants investigation because decision-time averages include only requests that have been accepted, rejected, or marked as duplicates. Pending and snoozed requests remain outside that calculation.
The Intake owner opens the project's queue and finds an older access request awaiting clarification, along with another submission that duplicates an existing work item. The team can obtain the missing information, accept the valid request into the project workflow, and mark the repeated submission as a duplicate. It can also introduce a regular review of ageing requests to prevent similar delays.
The Intake breakdown widget provides additional context on submission volumes across the app, email, and forms, helping the team assess which channels generate the most demand.
5. Release owner dashboard
Question: What could stop us from shipping on the target date?
A release owner needs to assess outstanding work, recorded blockers, and validation requirements before shipping. Plane's Releases feature maintains the release's scope and progress, while a supporting dashboard can highlight execution exceptions across the contributing projects.
Setup in Plane
Open the release's Scope to identify its associated work items and contributing projects. Select those projects as dashboard sources. If your team maintains a dedicated release-specific work item label, apply the appropriate label filter at dashboard level so the regular widgets use the same reporting subset.
For workspace releases spanning multiple projects, verify that the filter includes the intended work items from each project. Compare the results against the native Release Scope and update the supporting labels as release membership changes. Keep completed and unfinished work in the shared reporting scope, using widget-level filters to isolate specific exceptions.
Open Workspace → Releases → Select an upcoming release → Scope.
Show the release name and its linked work items from the participating projects. Make the work item states and outstanding items visible.
This screen will support the release-readiness example by showing the actual release scope inside Plane.
Recommended widgets
Plane widget | Configuration | What it shows |
Number | Work item count; filter to unfinished state groups within the validated release-related scope | Outstanding work in the selected reporting subset |
Number | Blocked work items; filter to unfinished state groups within the same scope | Unfinished items with recorded blocking dependencies |
Basic bar | X-axis: State group; Y-axis: Work item count; retain all relevant state groups within the same scope | State distribution of the selected release-related work |
Work items table | Filter to unfinished items within the same scope; display Releases, assignees, priority, state, and due date | Specific release-related items requiring follow-up before shipping |
Open Workspace → Dashboards → Release readiness dashboard.
Show a dashboard covering work associated with an upcoming release, with:
- Number: Outstanding release-related work items
- Number: Blocked work items
- Basic bar: Work items by state group
- Work items table with assignee, priority, state, and due date
Clearly identify the release being reviewed, for example, v2.4 release. Use an explicitly maintained and verified work item label or another supported filter to restrict the dashboard to the intended work.
Plan availability: Number and Basic bar widgets are available on Pro. Work items table and Plane Releases require Business.
What happens during the release review?
A team is getting ready to ship a mobile application update. The release's Scope includes a payment retry fix awaiting final validation and a lower-priority settings improvement. The supporting dashboard highlights the unfinished work, while the work items table identifies the responsible owners and current states.
During the release review, the owner confirms that regression testing has uncovered an unresolved payment retry failure. Because the issue affects a critical checkout flow, the team decides to delay shipping until the fix passes validation.
Once the issue is resolved and the required checks are complete, the release owner can proceed through Plane's Release now workflow. If the lower-priority improvement remains unfinished, the team can transfer it to another unreleased release, keeping the shipped release's scope aligned with the agreed delivery decision.
Four setup mistakes that skew dashboard numbers
1. Choosing a scope that's too broad or too mixed
Source projects decide what every widget can see, so an unrelated project inflates totals. Work item counts also treat a ten-minute fix and a two-week feature as one item each, so comparing a project that splits work finely with one that doesn't will mislead you. Decide three things before adding a widget: which projects contribute, which states, cycles, or modules count, and whether each number describes a whole project, one commitment, or a narrow exception. Then write that scope into the widget title, and use estimate points when effort matters more than volume.
2. Filtering the whole dashboard when one widget needs it
Plane applies filters in layers: dashboard filters first, then dashboard-level PQL, then widget filters, and a widget filter can only narrow what the layers above it allow. A filter set at dashboard level therefore reaches every widget.
Configuration | Effect |
Filter the whole dashboard to unfinished state groups | A Progress donut on that dashboard shows 0% complete, because the completed work it counts has been filtered out. |
Keep the full scope and filter only the overdue widget | Completion stays accurate, and the overdue widget shows only overdue items |
Open Workspace → Dashboards → Select a dashboard → Edit dashboard/widget configuration.
Show a dashboard with:
- Dashboard-level filters retaining the relevant work across state groups
- A Number widget configured to count only open or outstanding work items
- The widget-level filter settings clearly visible
The screen should demonstrate how the dashboard retains the full project scope while an individual widget counts a narrower set of work items.
This will be used in the section “Four setup mistakes that make a dashboard wrong.”
For one-off questions during a review, use the quick filters in the dashboard header. They sit on top of the saved configuration and clear when you reload. Every regular widget also leaves out Triage-state, archived, and draft work items, so expect totals to differ from a raw project count.
For conditions the standard filters can't express, such as isOverdue() (open items past their due date) or hasNoAssignee(), use PQL and check the query results against the underlying work items before using them in recurring reports.
3. Reading a metric for more than it measures
Metric | What it counts | How to read it |
Blocked work items | Items with a recorded Blocked by relationship | A prompt to open the dependency and judge its impact |
Work item count | Matching records, whatever their size | Volume; switch to estimate points for effort |
Work item type progress | Completion of direct sub-items, by count or estimate points | Show completed counts cancelled sub-items as done |
Intake decision time | Average time to accept, decline or mark duplicate | Pending and snoozed requests are excluded, so pair it with the ageing widget |
Release progress | Completed items in the release Overview, leaving cancelled items out of the total | Dashboard widgets may count differently, so treat the Overview as the source of truth |
Project health | On track, At risk and Off track labels | Lives in Analytics, separate from dashboards |
Time-based charts need the same care. Grouping by completed date shows how much work finished in each period, which is a different measure from how big the backlog was at the time.
4. Building on patchy work-item data
A dashboard can only be as accurate as the fields behind it.
If this is missing or inconsistent | This report goes wrong |
Due dates | Overdue and due-this-week counts miss commitments |
Blocking relationships | Blocker counts undercount real dependencies |
Priorities | High-priority views become unreliable |
States and state groups | Cross-project progress comparisons mislead |
Assignees | Ownership and workload views go blank |
Parent-child links | Epic progress leaves out work |
Modules and cycles | Workstream and iteration reports come up short |
Release membership | Release dashboards include or drop the wrong items |
Agree on field conventions across the projects a dashboard combines, and review a sample of the underlying work items every few weeks.
Before you commit: check plan, access and fit
Pick the plan that covers your widgets
Dashboards start on Pro, and Business adds the widgets that name owners and track progress in detail.
Capability | Minimum plan |
Dashboards with Number, Pie, Two-dimensional table, and the basic bar, line, area, and donut models | Pro ($6 per seat per month billed annually, $8 monthly) |
Stacked and grouped bar, multi-line, Work items table, Work items statistics, Smart Counter, Smart Gauge, Work item type progress, Cycle progress bar, Assigned to you | Business ($13 per seat a month billed annually, $15 monthly) |
All four Intake widgets, plus Intake by email and form | Business |
Releases | Business |
Private dashboards, sharing and publishing | Business |
Project health in Analytics, milestones and project updates | Pro |
Plane also supports PQL for advanced dashboard filtering.
In short, Pro gives you counts and cross-project comparisons, and Business adds the tables, progress, and workload widgets that four of the five dashboards above depend on. For self-hosted deployments, check your licence against the pricing page and the Dashboards docs.
Decide who sees what
Option | Who can see it | Who can change it |
Public (default) | All workspace members | The creator, workspace admins, and owners |
Private (Business) | Initially only the creator; selected workspace members can be granted access through sharing | The creator and members granted Edit access, subject to dashboard management permission |
Shared (Business) | Members you pick | Members you give Edit access, except for deleting it, changing visibility, or managing sharing |
Published (Business) | Anyone with the link, without signing in | Only the owner can publish, unpublish, or regenerate the link |
PDF export | Whoever receives the file | Static copy, in portrait or landscape |
Dashboard visibility and work-item permissions are separate, so open the dashboard from a reviewer's account before you rely on it. Treat a published link like a shared document. It has no password, expiry date, or view limit, so review what it shows before you send it. Regenerating the link cuts off the old one instantly, and unpublishing deactivates it until you turn it back on. Personal widgets such as Assigned to you show nothing on a published dashboard, because no one is signed in.
Run a real review on a trial workspace
The fastest way to judge fit is to rebuild one of your existing reports. Start a 14-day Plane Business trial on cloud, import or create two representative projects, and:
- Build it: Select both projects, add a Basic bar with Project on the x-axis and a Work items table filtered to unfinished High and Urgent work.
- Check it: Compare the counts and listed items with the project views to confirm the filters catch what you intended.
- Investigate one exception: Click a bar, open the work items behind it, and check their owners, states, and due dates.
- Test access: Open the dashboard from a teammate's account and confirm what they can and can't see.
- Decide: Ask whether the dashboard gave you enough to act on in your next real meeting.
Bottom line
If your team still assembles a status update by hand every week, start with the dashboard for your most important recurring review, whether that's an engineering meeting, a launch check-in, or a leadership sync. Run it from Plane for two weeks to see how well it supports the discussion. Supported chart elements also let reviewers open the matching work items to investigate issues in more detail.
Try Plane Business free for 14 days, or talk to our team for a live walkthrough built around your reporting workflow. More than 50,000 teams already plan their work in Plane.
Frequently asked questions
Q1. Can Plane dashboards combine work from multiple projects?
Yes. Plane Dashboards belong to a workspace and can use one or more selected projects as their data source. Regular widgets report on work items from those projects, subject to the configured dashboard and widget filters. This allows teams to create cross-project reports for engineering, delivery, and portfolio reviews.
Q2. Which Plane dashboard widgets are available on Pro and Business?
Pro includes Dashboards and basic widget models such as Number and Basic bar. Business adds advanced models, including Stacked bar, Work items table, Work item type progress, Cycle progress bar, and dedicated Intake widgets.
Q3. How do dashboard-level and widget-level filters work in Plane?
Dashboard-level filters establish the work available to regular widgets, while widget-level filters narrow the results for an individual widget. Plane applies dashboard filters, dashboard PQL, and widget filters as intersecting conditions. Header filters provide temporary filtering during a review.
Q4. Can dashboard viewers open the work items behind a chart?
Yes. In dashboard view mode, viewers can select supported chart elements, such as a bar, to open the matching work items. The resulting records reflect the dashboard's selected projects and applicable filters. Access to underlying work remains subject to the viewer's permissions.
Q5. Can Plane dashboards be shared with people outside the workspace?
Yes, where dashboard publishing is enabled. Published dashboards have a read-only URL that can be opened without signing in. Anyone with the link can view the published data, so teams should review its contents and access implications before sharing. Plane also supports workspace sharing and static PDF export.
Recommended for you

.webp&w=3840&q=75&dpl=dpl_6iq8A8f73qrxWNCrmwutwhSoVJNE)

