Work Hub dashboard
Open planning, analytics, risks and daily-work tools from one starting point.
Find the tools that take effort out of Jira.
From project planning to the last worklog.
Edition labels show where support is documented. A missing label means support is not confirmed here. Features and Jira integration differ by edition. Compare editions.
83 documented capabilities
Try a different search or edition.
Open your tools and return to your own work from one starting point.
Open planning, analytics, risks and daily-work tools from one starting point.
Add personal shortcuts and hide dashboard tiles you do not need.
Open the browser edition’s KPI dashboard. Available metrics depend on its configuration.
Open Work Hub from Jira’s navigation. In the browser edition, choose whether its menu entry is shown.
Manage the Cloud app from its dedicated administration page.
See Jira issues, relationships and key dates on one timeline.
Create named plans and select their Jira issues using saved JQL searches.
Choose the Jira fields for start and end dates, then set the visible date range.
See dates and status colors together on a Gantt timeline.
See the relationships between tasks in the plan.
Mark important dates alongside your work.
Add planning elements and phases alongside Jira issues.
Group related work. In Cloud, task ordering preserves the plan hierarchy.
Set planning dates manually in the Data Center planner.
Move or resize Cloud tasks to update dates, with checks that the fields are editable.
Schedule Cloud tasks across weekdays while accounting for dependencies.
Use multi-select quick filters to focus the Cloud plan.
Organize Data Center plans in folders and move plans between them.
Bring source plans together in the Data Center planner.
Save or restore Data Center plan data, including dates, flags, groups and local items.
Compare project workloads across the stages of your workflow.
Compare work across projects and configurable workflow columns.
Review open, to-do, in-progress and recently completed issue counts.
See unassigned, overdue and recently updated issues.
Define JQL queries for projects and columns, with named metrics such as blockers or missing estimates.
Change Funnel column names and symbols to reflect your own workflow.
Review saved Funnel and capacity-lane history.
Compare planned capacity with recorded work.
Compare planned capacity by configured role or skill lane across future periods.
Import a supported Excel planning export into the capacity overview.
Import Tempo or Jira booking CSV files to analyze recorded work.
Read Tempo Data Center bookings through Jira worklogs, using the current Jira user’s permissions.
Copy a summary of next week’s capacity to share in Microsoft Teams.
Keep explicitly synchronized Cloud booking history private and outside shared solutions. Clear it separately when needed.
Review service workload and performance using configurable Jira queues.
Configure Jira projects as queues for service analysis.
Explore configurable service analytics based on Jira searches.
Review issue age, created-issue trends and completion duration.
See priority breakdowns and status distributions for service work.
Add your Jira SLA custom fields through dashboard settings.
Review risk, impact and treatment alongside the work.
Review project risks in the Risk Register and its dashboard.
See how many risks are open or highly rated.
Review risks in a matrix of impact and probability.
Compare risks by category and treatment.
Group financial exposure into configurable bands.
See how risk changes over time.
Filter the risk table and follow links back to Jira issues.
Choose the Jira project, issue type and fields used by the Risk Register.
Review risk and financial responsibility by role.
Open Risk Overview alongside the Risk Register.
Configure roles and the projects relevant to each role.
Set financial approval limits by role and highlight risks that exceed those limits.
Review financial risk bands across projects visible to your Jira account.
Review your day and record work against Jira issues.
Track time while a Jira ticket is visible in the active browser window. The documented Data Center tracker pauses after five minutes without activity.
Choose a day to review tracked minutes, visited tickets and unbooked time.
Adjust minutes for meetings or offline work and add a description before booking.
Create Jira worklogs for remaining tracked time. Tempo Data Center reads the same worklogs.
Remember booked minutes to help avoid booking the same tracked time twice.
Create Jira worklogs manually in the Cloud edition.
In the browser edition, review your own ticket changes and comments for the selected day.
Read, expand or refresh your activity summary without changing tracked minutes or worklogs.
Reduce repeated steps when choosing labels and preparing comments.
Choose from configured label suggestions. In Cloud, the full controls are in the Work Hub issue panel.
Organize suggestions by role, including project, development, quality, support and operations.
Limit label suggestions to the relevant projects and Jira issue types.
Import or export label-suggestion settings as JSON.
Prepare comment text in the Work Hub issue panel.
Show contextual label hints on supported native Jira screens while keeping the full controls in the issue panel.
After a Jira mention event, Cloud can correct a saved comment’s visibility. It cannot intercept every comment submitted through Jira’s own screens.
Check whether the people you mention can read your comment.
Check whether mentioned people can read a restricted Jira comment in the browser add-on.
See which mentioned people cannot read the comment and the restriction currently applied.
Keep the restriction or change the comment to All Users before posting. This changes comment visibility within Jira; it does not grant access to a restricted issue.
Choose whether the checker should automatically switch to All Users when a mentioned person cannot read a restricted comment.
If the browser checker cannot verify a mentioned person’s access, it stops the comment from being posted.
Optionally prepare new comments with a configurable greeting, closing and signature name.
Cloud uses the Work Hub issue panel and can correct visibility after a Jira mention event. It cannot pause every comment submitted through Jira’s own screens.
Share a useful view with your team or prepare it for a meeting.
Share supported toolkit settings and project-bound plans through the app’s token-based sharing. Jira data is still read with each user’s permissions.
Share plans with Jira people, groups or project audiences.
Control Cloud plan access with view and edit roles and a member list.
Review activity history for Cloud plan sharing.
Export Data Center project-plan information as CSV.
Export a Data Center plan view as an image.
Export Data Center project plans for a PowerPoint presentation.
Use Work Hub within your existing Jira permissions and environment.
Read Jira work in the signed-in user’s context, within existing issue and project permissions.
Keep browser plans, settings and KPI cache data in the current browser profile. Plans remain personal, with no team-sharing controls.
Store plans and preferences in Forge hosted storage, separated by Atlassian account. Other Jira issue data is requested as the user.
Store app scenarios and user settings in Jira plugin storage, with revision-aware profile updates in the available P2 source.
Use the browser bundle without Tampermonkey, the Work Hub server app or a localhost file server.
The browser extension is available for Firefox, Safari and Chrome, with browser-specific installation packages. The documented Chromium setup also includes Microsoft Edge.
See how the tools work together in the product introduction.
Watch the introduction