Dashboard Widgets
SetGet dashboards ship with 27 purpose-built widget types. Each widget is designed around a specific question a project manager, team lead, or individual contributor might ask during a workday. This page documents every widget, what it shows, when it is most useful, where its data comes from, and how to configure it.
Widget quick-reference table
| # | Widget | Category | Default size |
|---|---|---|---|
| 1 | Overview Stats Bar | Summary | Full width |
| 2 | Workspace Health Score | Summary | 1x1 |
| 3 | Issues by State Chart | Distribution | 2x2 |
| 4 | Issues by Priority Chart | Distribution | 2x2 |
| 5 | Issues by Label Chart | Distribution | 2x2 |
| 6 | Team Workload Widget | People | 2x2 |
| 7 | Module Progress Widget | Planning | 2x1 |
| 8 | Activity Heatmap | Activity | 2x2 |
| 9 | Issues Due Soon | Lists | 2x2 |
| 10 | Activity Timeline | Activity | 2x2 |
| 11 | Quick Actions Panel | Utility | 1x1 |
| 12 | Risk Alerts Panel | Health | 2x1 |
| 13 | Scope Creep Chart | Trends | 2x2 |
| 14 | Project Health Matrix | Health | 2x2 |
| 15 | Cycle Risk Cards | Planning | 2x1 |
| 16 | Member Completion Rates | People | 2x2 |
| 17 | Velocity Trend Chart | Trends | 2x2 |
| 18 | Hot Issues | Lists | 2x2 |
| 19 | Stalled Issues | Lists | 2x2 |
| 20 | Welcome Banner | Utility | Full width |
| 21 | Workspace Summary | Summary | Full width |
| 22 | Issue Age Distribution | Distribution | 2x2 |
| 23 | Deadline Calendar Strip | Calendar | Full width |
| 24 | Assignee Distribution | Distribution | 2x2 |
| 25 | Recent Items | Utility | 1x2 |
| 26 | Active Cycles Widget | Planning | 2x1 |
| 27 | Custom Query Widget | Advanced | 2x2 |
1. Overview Stats Bar
What it shows
A horizontal bar spanning the full dashboard width, displaying key issue counts at a glance:
| Metric | Description |
|---|---|
| Total issues | Count of all issues in scope |
| Completed | Issues in a completed state |
| Pending | Issues awaiting action or review |
| Cancelled | Issues that were cancelled |
| Started | Issues currently in progress |
| Backlog | Issues in the backlog state |
| Unstarted | Issues created but not yet moved to any active state |
Each metric is displayed as a large number with a label beneath it. Percentage change compared to the previous period is shown as a small green or red indicator.
When to use it
Place this widget at the top of any dashboard where stakeholders need a quick numeric snapshot of workspace or project health before diving into charts.
Data source
Aggregates issue state counts from all projects in the workspace, or from a filtered subset of projects if configured.
Configuration options
| Option | Description | Default |
|---|---|---|
| Scope | Workspace-wide or selected projects | Workspace |
| Comparison period | Previous week, month, or quarter | Previous week |
| Show percentages | Display percentage alongside raw counts | Off |
| Highlight threshold | Colour a metric red when it exceeds a threshold | None |
2. Workspace Health Score
What it shows
A single composite score from 0 to 100 displayed in a radial gauge. The score is calculated from several factors:
| Factor | Weight | Description |
|---|---|---|
| Overdue ratio | 30% | Percentage of issues past their due date |
| Completion velocity | 25% | Rate of issue completion vs. creation |
| Stalled ratio | 20% | Percentage of issues with no activity in 7+ days |
| Unassigned high-priority ratio | 15% | High/urgent issues without an assignee |
| Cycle on-track ratio | 10% | Percentage of active cycles on schedule |
When to use it
Useful for executive dashboards where a single health indicator replaces a wall of charts. Combine with the Risk Alerts Panel for drill-down.
Data source
Workspace-wide aggregation recalculated every 15 minutes. Uses the dashboard_health aggregation pipeline.
Configuration options
| Option | Description | Default |
|---|---|---|
| Scope | Workspace or selected projects | Workspace |
| Score thresholds | Green/yellow/red cutoff values | 75 / 50 |
| Show breakdown | Display factor scores below the gauge | Off |
3. Issues by State Chart
What it shows
A pie chart or donut chart showing the distribution of issues across workflow states (Backlog, Unstarted, Started, In Review, Done, Cancelled, etc.). Each slice is colour-coded to match the state colour configured in project settings.
When to use it
Best for standup dashboards and sprint reviews where the team needs to see how work is distributed across pipeline stages.
Data source
Queries the issues collection grouped by state_id. Respects project filters if configured.
Configuration options
| Option | Description | Default |
|---|---|---|
| Chart type | Pie, donut, or horizontal bar | Donut |
| Scope | Workspace, project, or cycle | Workspace |
| Exclude states | Hide specific states from the chart | None |
| Show counts | Display numbers on each slice | On |
| Show legend | Toggle the legend panel | On |
4. Issues by Priority Chart
What it shows
A bar chart or pie chart breaking down issues by priority level: Urgent, High, Medium, Low, and None. Bars are colour-coded (red for Urgent, orange for High, yellow for Medium, blue for Low, grey for None).
When to use it
Sprint planning sessions where the team needs to understand the priority mix before committing to work. Also valuable for managers monitoring whether high-priority items are accumulating.
Data source
Groups issues by the priority field. Workspace-wide or scoped to selected projects.
Configuration options
| Option | Description | Default |
|---|---|---|
| Chart type | Bar (horizontal/vertical) or pie | Vertical bar |
| Scope | Workspace, project, or cycle | Workspace |
| Exclude priorities | Hide specific priority levels | None |
| Sort order | By count or by priority rank | Priority rank |
| Show trend | Overlay a trend line for the past N periods | Off |
5. Issues by Label Chart
What it shows
A pie chart or tag cloud showing how issues are distributed across labels. Labels inherit their colour from workspace or project label settings.
When to use it
Useful for teams that use labels to categorize work types (bug, feature, tech-debt, design) and want to understand the mix.
Data source
Groups issues by label_ids. An issue with multiple labels is counted once per label. Workspace-wide or project-scoped.
Configuration options
| Option | Description | Default |
|---|---|---|
| Chart type | Pie, donut, horizontal bar, or tag cloud | Horizontal bar |
| Scope | Workspace or project | Workspace |
| Max labels | Number of labels to show before grouping as "Other" | 10 |
| Sort | By count or alphabetical | By count |
6. Team Workload Widget
What it shows
A stacked horizontal bar chart where each bar represents a team member. The bar is segmented by issue state (backlog, started, in review, etc.), showing how many issues each person has in each state.
When to use it
Capacity planning and load balancing. Use during sprint planning to check whether work is evenly distributed or if some members are overloaded.
Data source
Queries issues grouped by assignee_id and state_id. Only counts issues in non-completed states by default.
Configuration options
| Option | Description | Default |
|---|---|---|
| Scope | Workspace, project, or cycle | Workspace |
| Include completed | Show completed issues in the bars | Off |
| Sort | By total count or alphabetical | By total count |
| Max members | Limit the number of members displayed | 15 |
| Show avatars | Display member avatars next to names | On |
7. Module Progress Widget
What it shows
A list of modules with a progress bar for each. The progress bar shows the percentage of issues completed out of total issues in the module. Each module displays:
| Field | Description |
|---|---|
| Module name | The module title |
| Progress bar | Visual completion percentage |
| Completed / Total | Numeric count (e.g., "12 / 20") |
| Status indicator | On track, at risk, or behind |
When to use it
Product managers tracking feature delivery across multiple modules. Place alongside the Cycle Risk Cards for a full planning picture.
Data source
Aggregates issue completion counts per module from the modules and module_issues collections.
Configuration options
| Option | Description | Default |
|---|---|---|
| Scope | All modules or selected project | All modules |
| Sort | By progress percentage or by name | By progress |
| Show status | Display the on-track/at-risk indicator | On |
| Max modules | Limit displayed modules | 10 |
8. Activity Heatmap
What it shows
A grid-based heatmap with days of the week on the Y-axis and hours of the day on the X-axis. Each cell is colour-coded by the volume of activity (issue updates, comments, state changes) during that hour-day combination.
When to use it
Understanding team work patterns. Identify peak productivity hours, detect after-hours work, and plan meetings around high-activity periods.
Data source
Aggregates the activity_log collection by created_at timestamp, bucketed into day-of-week and hour-of-day. Uses the workspace timezone setting.
Configuration options
| Option | Description | Default |
|---|---|---|
| Period | Last 7 days, 30 days, or 90 days | 30 days |
| Activity type | All activity, state changes only, or comments only | All |
| Colour scale | Sequential green, blue, or heat (red-yellow) | Green |
| Timezone | Override workspace timezone | Workspace default |
9. Issues Due Soon
What it shows
A list of issues with approaching deadlines, sorted by due date ascending. Each row shows:
| Column | Description |
|---|---|
| Issue identifier | Project prefix and issue number |
| Title | Issue title (truncated) |
| Assignee | Avatar and name |
| Due date | Calendar date with "in X days" label |
| Priority | Priority badge |
| State | Current state badge |
Issues due today are highlighted in red. Issues due within 3 days are highlighted in orange.
When to use it
Daily standups and personal dashboards. Keeps upcoming deadlines visible so nothing slips through.
Data source
Queries issues where due_date is within the configured window and state is not completed or cancelled.
Configuration options
| Option | Description | Default |
|---|---|---|
| Window | Number of days ahead to look | 7 |
| Scope | Workspace, project, or assigned to me | Workspace |
| Max items | Limit the list length | 10 |
| Show overdue | Include past-due items at the top | On |
10. Activity Timeline
What it shows
A chronological feed of recent workspace activity. Each entry shows:
| Field | Description |
|---|---|
| Timestamp | When the activity occurred |
| Actor | Who performed the action (avatar and name) |
| Action | What happened (created, updated, commented, etc.) |
| Target | The issue, page, or module affected |
| Detail | Brief description of the change |
When to use it
Monitoring dashboards and team awareness screens. Helps managers and leads stay informed about what is happening across the workspace without checking individual issues.
Data source
Reads from the activity_log collection, ordered by created_at descending. Supports filtering by project and activity type.
Configuration options
| Option | Description | Default |
|---|---|---|
| Scope | Workspace or project | Workspace |
| Activity types | Filter to specific action types | All |
| Max entries | Number of entries to display | 15 |
| Show avatars | Display member avatars | On |
| Compact mode | Single-line entries without detail | Off |
11. Quick Actions Panel
What it shows
A grid of shortcut buttons for common workflow actions:
| Action | Description |
|---|---|
| Create issue | Opens the new issue modal |
| Start timer | Starts the time tracking timer |
| Log time | Opens the manual time entry modal |
| Create page | Opens a new page in the wiki |
| Go to my issues | Navigates to your assigned issues view |
| Go to active cycle | Navigates to the current active cycle |
When to use it
Personal dashboards where you want fast access to daily actions without navigating through the sidebar.
Data source
No data aggregation. This is a utility widget with static actions.
Configuration options
| Option | Description | Default |
|---|---|---|
| Actions | Choose which actions to display | All |
| Layout | Grid (2x3) or list | Grid |
| Show labels | Display text labels below icons | On |
12. Risk Alerts Panel
What it shows
A set of alert cards, each showing a risk metric with a count and a severity colour:
| Alert | Description | Severity trigger |
|---|---|---|
| Overdue issues | Issues past their due date | Count > 0 |
| Stalled issues | Issues with no activity for 7+ days | Count > 5 |
| Unassigned high priority | Urgent/High issues without an assignee | Count > 0 |
| Missing due dates | In-progress issues without a due date | Count > 10 |
Each card shows the count prominently, with a red/yellow/green background depending on the severity threshold.
When to use it
Management dashboards where early warning of project risks is critical. Pair with the Workspace Health Score for a combined view.
Data source
Runs four aggregation queries against the issues collection with the appropriate filters for each risk type.
Configuration options
| Option | Description | Default |
|---|---|---|
| Scope | Workspace or project | Workspace |
| Stalled threshold | Days of inactivity before an issue is "stalled" | 7 |
| Missing due date scope | Only in-progress, or all non-completed | In-progress only |
| Custom thresholds | Set yellow/red thresholds per alert type | Default |
WARNING
Risk alerts use point-in-time counts. A stalled issue count of zero does not mean no issues were stalled during the week -- it means none are stalled right now.
13. Scope Creep Chart
What it shows
A line chart with weekly data points showing two lines:
| Line | Description |
|---|---|
| Issues added | Number of issues created or added to the cycle/project each week |
| Issues completed | Number of issues completed each week |
The gap between the two lines indicates scope creep when additions outpace completions.
When to use it
Sprint retrospectives and project reviews. Helps teams identify periods where scope expanded faster than delivery.
Data source
Aggregates issues by created_at and completed_at timestamps, grouped by ISO week. Can be scoped to a cycle, project, or workspace.
Configuration options
| Option | Description | Default |
|---|---|---|
| Period | Number of weeks to display | 12 |
| Scope | Workspace, project, or cycle | Workspace |
| Show net change | Add a third line for net (added minus completed) | Off |
| Cumulative mode | Show running totals instead of weekly counts | Off |
14. Project Health Matrix
What it shows
A table where each row is a project and each column is a health indicator:
| Column | Description |
|---|---|
| Project name | The project title |
| Open issues | Count of non-completed issues |
| Overdue | Count of issues past due date |
| Completion rate | Percentage of issues completed in the last 30 days |
| Velocity | Average issues completed per week |
| Health | Colour-coded badge (green, yellow, red) |
The health badge is calculated from the combination of overdue ratio and completion rate.
When to use it
Portfolio-level dashboards where a manager oversees multiple projects and needs a single view to identify which projects need attention.
Data source
Queries the issues collection grouped by project_id with aggregation pipelines for each metric column.
Configuration options
| Option | Description | Default |
|---|---|---|
| Projects | All or selected projects | All |
| Sort | By health score, name, or open count | By health score |
| Show sparklines | Mini trend charts in each cell | Off |
| Period | Lookback period for velocity and completion rate | 30 days |
15. Cycle Risk Cards
What it shows
A horizontal row of cards, one per active cycle. Each card displays:
| Field | Description |
|---|---|
| Cycle name | The cycle title |
| Progress | Percentage of issues completed |
| Days remaining | Calendar days until cycle end |
| Burn rate | Whether the team is ahead, on track, or behind ideal pace |
| Scope changes | Number of issues added/removed since cycle start |
Cards are colour-coded: green for on track, yellow for at risk, red for behind.
When to use it
Sprint-centric teams that run multiple cycles in parallel. Place on a standup dashboard alongside the Team Workload Widget.
Data source
Reads from the cycles and cycle_issues collections. Compares current completion against the ideal linear burndown.
Configuration options
| Option | Description | Default |
|---|---|---|
| Scope | All active cycles or selected project | All active |
| Show completed cycles | Include recently completed cycles | Off |
| Risk thresholds | Define "at risk" and "behind" percentages | 10% / 25% behind ideal |
16. Member Completion Rates
What it shows
A table or bar chart showing individual member productivity metrics:
| Metric | Description |
|---|---|
| Member name | Name and avatar |
| Issues completed | Count in the selected period |
| Completion rate | Percentage of assigned issues completed |
| Average time to close | Mean time from assignment to completion |
| Trend | Sparkline showing weekly completion counts |
When to use it
Performance reviews and team retrospectives. Helps identify members who may need support or recognition.
Data source
Aggregates issues by assignee_id and completed_at, scoped to the selected period and projects.
Configuration options
| Option | Description | Default |
|---|---|---|
| Period | Last 7, 30, or 90 days | 30 days |
| Scope | Workspace or project | Workspace |
| Display | Table or bar chart | Table |
| Sort | By completion count or rate | By count |
| Max members | Limit displayed members | 15 |
TIP
Completion rates are most meaningful when compared against workload. A member with a 50% completion rate who has 40 assigned issues may be more productive than a member with 100% who has 5.
17. Velocity Trend Chart
What it shows
A line chart plotting the number of issues (or story points, if estimates are used) completed per week or per cycle over time. An optional trend line shows the moving average.
When to use it
Long-term planning and capacity estimation. Teams use velocity trends to predict how much work they can take on in future cycles.
Data source
Aggregates completed issues by week or by cycle. Uses completed_at timestamps and optional estimate values.
Configuration options
| Option | Description | Default |
|---|---|---|
| Unit | Issue count or estimate points | Issue count |
| Granularity | Per week or per cycle | Per week |
| Period | Number of weeks/cycles to display | 12 |
| Show trend line | Moving average overlay | On |
| Scope | Workspace or project | Workspace |
18. Hot Issues
What it shows
A ranked list of the most active issues, determined by recent activity volume. Each entry shows:
| Column | Description |
|---|---|
| Issue identifier | Project prefix and number |
| Title | Issue title |
| Activity count | Number of updates, comments, and state changes in the period |
| Last activity | Timestamp of the most recent action |
| Assignee | Current assignee |
| Priority | Priority badge |
When to use it
Identifying issues that are generating significant discussion or frequent changes. Useful for managers to spot items that may need escalation or attention.
Data source
Counts entries in the activity_log collection per issue, ranked by count descending.
Configuration options
| Option | Description | Default |
|---|---|---|
| Period | Lookback window for activity counting | 7 days |
| Scope | Workspace or project | Workspace |
| Max items | Number of issues to display | 10 |
| Exclude bots | Filter out automated activity | On |
19. Stalled Issues
What it shows
A list of issues that have had no activity for a configurable number of days. Each entry shows:
| Column | Description |
|---|---|
| Issue identifier | Project prefix and number |
| Title | Issue title |
| Last activity | Date of the last update |
| Days stalled | Number of days since last activity |
| Assignee | Current assignee (or "Unassigned") |
| State | Current state badge |
Issues are sorted by days stalled, descending, so the most neglected items appear first.
When to use it
Backlog grooming and triage sessions. Stalled issues may need re-prioritization, reassignment, or closure.
Data source
Queries issues where the most recent activity_log entry is older than the stalled threshold and the issue is not in a completed or cancelled state.
Configuration options
| Option | Description | Default |
|---|---|---|
| Stalled threshold | Minimum days of inactivity | 7 |
| Scope | Workspace or project | Workspace |
| Max items | Limit the list | 10 |
| Exclude backlog | Ignore issues in the backlog state | Off |
20. Welcome Banner
What it shows
A personalized greeting banner at the top of the dashboard. It includes:
| Element | Description |
|---|---|
| Greeting | "Good morning/afternoon/evening, [Name]" |
| Date | Today's date in a human-readable format |
| Weekly stats | Issues completed this week, issues due this week, hours logged |
| Motivational nudge | Contextual tip based on workload ("You have 3 items due today") |
When to use it
Personal dashboards. The Welcome Banner provides a gentle daily briefing before the user dives into detailed widgets.
Data source
Reads the current user's profile, and aggregates their assigned issues and time logs for the current week.
Configuration options
| Option | Description | Default |
|---|---|---|
| Show weekly stats | Toggle the stats row | On |
| Show nudge | Toggle the contextual tip | On |
| Greeting style | Formal ("Good morning") or casual ("Hey") | Formal |
21. Workspace Summary
What it shows
A full-width bar showing aggregate counts for the workspace:
| Metric | Description |
|---|---|
| Projects | Total number of active projects |
| Active cycles | Number of currently running cycles |
| Members | Count of workspace members |
| Pages | Total wiki pages |
| Modules | Total modules across all projects |
| Issues | Total non-archived issues |
Each metric is displayed as a large number with an icon.
When to use it
Onboarding dashboards and executive views. Provides a birds-eye count of workspace contents.
Data source
Counts documents in the projects, cycles, workspace_memberships, pages, modules, and issues collections.
Configuration options
| Option | Description | Default |
|---|---|---|
| Metrics | Choose which counts to display | All |
| Show change | Display change vs. previous period | Off |
22. Issue Age Distribution
What it shows
A histogram showing how long open issues have existed, bucketed by age ranges:
| Bucket | Range |
|---|---|
| Fresh | 0 - 7 days |
| Recent | 8 - 14 days |
| Moderate | 15 - 30 days |
| Aging | 31 - 60 days |
| Old | 61 - 90 days |
| Ancient | 90+ days |
The X-axis shows the buckets, and the Y-axis shows the count of issues in each bucket.
When to use it
Backlog health assessments. A heavy concentration in the "Old" and "Ancient" buckets suggests the backlog needs cleanup.
Data source
Calculates the age of each open issue as the difference between now and created_at, then buckets the results.
Configuration options
| Option | Description | Default |
|---|---|---|
| Scope | Workspace or project | Workspace |
| Custom buckets | Override the default age ranges | Default ranges |
| Exclude backlog | Ignore backlog-state issues | Off |
| Chart type | Histogram or pie | Histogram |
23. Deadline Calendar Strip
What it shows
A horizontal calendar strip spanning the next 14 days (configurable). Each day cell shows the count of issues due on that date and a coloured indicator:
| Colour | Meaning |
|---|---|
| Green | 1-3 issues due |
| Yellow | 4-7 issues due |
| Red | 8+ issues due |
| Grey | No issues due |
Clicking a day cell reveals a dropdown listing the specific issues due on that date.
When to use it
Sprint dashboards and personal planning views. Provides a visual timeline of upcoming delivery pressure.
Data source
Queries issues with due_date in the configured window. Groups by date.
Configuration options
| Option | Description | Default |
|---|---|---|
| Window | Number of days to display | 14 |
| Scope | Workspace, project, or assigned to me | Workspace |
| Show overdue | Highlight past dates with overdue items | On |
| Colour thresholds | Customize green/yellow/red cutoffs | 3 / 7 |
24. Assignee Distribution
What it shows
A pie chart or bar chart showing how many open issues are assigned to each team member. An "Unassigned" slice represents issues with no assignee.
When to use it
Load balancing during sprint planning. Quickly spot uneven distribution or a large unassigned pool.
Data source
Groups issues by assignee_id where state is not completed or cancelled.
Configuration options
| Option | Description | Default |
|---|---|---|
| Chart type | Pie, donut, or bar | Donut |
| Scope | Workspace or project | Workspace |
| Max members | Group smaller counts as "Other" | 10 |
| Include unassigned | Show the unassigned count | On |
| Sort | By count or alphabetical | By count |
25. Recent Items
What it shows
A list of items the current user recently visited or interacted with:
| Column | Description |
|---|---|
| Item type | Issue, page, cycle, or module icon |
| Title | Item title |
| Project | Project the item belongs to |
| Last visited | Relative timestamp ("2 hours ago") |
When to use it
Personal dashboards for quick navigation back to items you were recently working on.
Data source
Reads from the user's recent activity stored in Redis, falling back to the activity_log collection filtered to the current user.
Configuration options
| Option | Description | Default |
|---|---|---|
| Max items | Number of recent items to show | 8 |
| Item types | Filter to specific types (issues, pages, etc.) | All |
| Show project | Display the project column | On |
26. Active Cycles Widget
What it shows
A compact summary of all currently active cycles (sprints):
| Field | Description |
|---|---|
| Cycle name | The sprint title |
| Date range | Start and end dates |
| Progress | Completion percentage with a mini progress bar |
| Issues | Completed / total issue count |
| Days left | Remaining calendar days |
When to use it
Teams running multiple sprints across projects. Provides at-a-glance sprint status without navigating to each cycle individually.
Data source
Queries the cycles collection where start_date <= now <= end_date. Joins with cycle_issues for completion counts.
Configuration options
| Option | Description | Default |
|---|---|---|
| Scope | All projects or selected project | All |
| Sort | By end date or by progress | By end date |
| Show completed | Include cycles completed in the last 7 days | Off |
27. Custom Query Widget
What it shows
A fully configurable widget where you define the data query, grouping, and visualization. This is the most flexible widget type and can replicate the functionality of any other widget or create entirely new views.
When to use it
Advanced users who need a view not covered by the 26 built-in widgets. Examples include filtering issues by a specific label AND priority, or tracking a custom metric over time.
Data source
Executes a user-defined aggregation query against the issues, activity_log, or time_logs collections.
Configuration options
| Option | Description | Default |
|---|---|---|
| Data source | Issues, activity, or time logs | Issues |
| Filters | Any combination of state, priority, assignee, label, project, date range | None |
| Group by | Field to group results (state, priority, assignee, label, project, etc.) | None |
| Metric | Count, sum of estimates, or sum of time logged | Count |
| Visualization | Bar, pie, line, area, number, or table | Bar |
| Date range | Time window for the query | Last 30 days |
| Title | Custom widget title | "Custom Query" |
Adding widgets to a dashboard
- Open a dashboard and enter Edit mode by clicking the Edit button.
- Click Add Widget in the toolbar.
- Browse the widget catalogue organized by category (Summary, Distribution, People, Planning, Activity, Lists, Utility, Health, Trends, Calendar, Advanced).
- Click a widget to add it.
- Configure the widget in the settings panel that appears.
- Click Save Widget.
- Drag the widget to your preferred position on the grid.
- Click Done to exit edit mode.
TIP
You can add multiple instances of the same widget type with different configurations. For example, add two Issues by State Chart widgets -- one scoped to Project A and one scoped to Project B.
Removing a widget
- Enter edit mode.
- Hover over the widget.
- Click the X button in the top-right corner.
- The widget is removed immediately. This action cannot be undone, but you can re-add the widget.
Widget categories summary
| Category | Widgets | Purpose |
|---|---|---|
| Summary | Overview Stats Bar, Workspace Health Score, Workspace Summary | High-level numeric snapshots |
| Distribution | Issues by State, Priority, Label, Assignee Distribution, Issue Age | How work is spread across dimensions |
| People | Team Workload, Member Completion Rates | Member-centric metrics |
| Planning | Module Progress, Cycle Risk Cards, Active Cycles | Delivery tracking |
| Activity | Activity Heatmap, Activity Timeline | Team behaviour and event log |
| Lists | Issues Due Soon, Hot Issues, Stalled Issues | Actionable issue lists |
| Utility | Quick Actions, Welcome Banner, Recent Items | Navigation and shortcuts |
| Health | Risk Alerts Panel, Project Health Matrix | Risk identification |
| Trends | Scope Creep Chart, Velocity Trend Chart | Longitudinal analysis |
| Calendar | Deadline Calendar Strip | Time-based deadline view |
| Advanced | Custom Query Widget | Fully configurable |