A dashboard sorted by decisions, delivery metrics, and better bulk actions

This update cleans up three surfaces that filled up over time: the dashboard, the notification panel and Planning & Reports. On top of that, two new capabilities on tickets themselves — an hour budget with fixed-price billing, and considerably more bulk actions.

Dashboard: four sections instead of fourteen

The dashboard used to render fourteen fixed sections in a fixed order. Anyone who had their own tickets and owned projects got both blocks stacked — in practice 15 to 18 cards on one page. The sections were also cut along the queries that produced them, not along what you have to do with them.

There are now four buckets, each answering exactly one question:

Four numbers sit at the top, one per bucket. Clicking one jumps to that bucket. Every bucket collapses — and the state sticks, across navigation and across sessions.

"Stuck" now tells you what it's waiting for

Blocked tickets, tickets with no customer reply, pending approvals, waiting agents and unassigned tickets used to be five separate sections. They are one list now, and every row carries a reason chip:

• waiting 4 d for approval from Anna
• blocked for 12 d by PRJ-142
• agent waiting 2 d for a reply
• no customer reply for 9 d
• unassigned for 21 d

A ticket now also counts as blocked when it simply sits in a status of the Blocked category — not only when it carries an "is blocked by" link.

If a ticket matches several reasons it is listed once, under the most specific one. The same rule applies across buckets: what shows under "Stuck" does not show up again under "In flight".

My work or Oversight — no longer both at once

If you own at least one project, there's a toggle in the top right:

• My work — your own state: what's waiting on you, what you have in progress, what's stuck.
• Oversight — the triage queue for your projects. "Waiting on you" here means new, untriaged or unassigned tickets.

Your choice is remembered. If you don't own a project, the toggle isn't shown and you stay on "My work".

Personal todos, active runners, budget alerts, time approvals and the news list stay as their own cards — they aren't ticket work.

Notifications: "Important" is the new default

The panel gained a third tab, and it is the new default view:

• Important (default) — only what a person addressed to you or what blocks your work: mentions, assignments, delegated todos, invitations, budget approval requests, required approvals, agents waiting for input, blocked tickets, rejected budgets, failed runner jobs, exceeded budgets, your own todo reminders.
• Unread — everything unread, including automatic reminders.
• All — the full history.

The bell badge now counts only important unread notifications. If your number dropped noticeably, that's why — automatic reminders used to keep it permanently lit.

Mark all as read now applies to the tab you are actually looking at. From "Important", informative notifications stay unread instead of being quietly swept away with the rest.

Recurring reminders no longer pile up

Reminders about idle tickets, blocked tickets, requested approvals and personal todos describe a state, not an event. So they no longer add a row per run: as long as an unread reminder of the same kind exists for the same ticket, it is updated in place, gets a counter and moves back to the top. The title states the current situation ("no activity for 77 days") rather than the event from back then.

Reading it resets the counter — the next run creates a fresh row if the condition still holds.

Snooze right in the list

Every notification row tied to a ticket now has a snooze action (visible on hover). And a snoozed ticket is finally quiet everywhere: budget reminders, todo reminders, budget approvals and explainability reminders used to ignore snoozing altogether.

Only informative notifications are snoozed. Something a person sent you directly — a mention, an assignment, an approval request — still comes through.

Overview: delivery metrics under Planning & Reports

Planning & Reports had four tabs — workload, budgets, time & budget, timeline — and not a single metric on whether delivery is on track. The new first tab, Overview, closes that gap. Period selectable: 4, 12 or 26 weeks.

Five KPIs at the top:

• Throughput — tickets completed per week, with the change against the previous period
• Lead time — median days from creation to completion, plus the p85 value
• On-time delivery — share delivered on time, of the tickets that have a due date
• Overdue — open tickets past their due date, plus the age of the oldest
• Reopen rate — share of tickets reopened after being completed

Three lists below:

• Where work piles up — open tickets per status with average age. That's the answer to "where does it jam".
• Sitting longest — the oldest tickets in their current status.
• Team — per person: open tickets, waiting tickets, estimated hours, booked hours and — where weekly hours are on file — utilization.

Metrics without a basis deliberately render "—" instead of a zero. A freshly enabled metric showing 0 reads like a perfect score. A note at the top therefore states since when data has been collected, and the Utilization column stays empty as long as no weekly hours are stored per person.

For admins: the tab sits behind the new reports:view permission. It is granted to the Administrators group by default only, because these metrics aggregate across every project the viewer can reach and expose per-person load. To let a team member see the Overview, enable reports:view for their permission group under Settings → Roles & Permissions. The permission is deliberately separate from timeline:view.

Four new widgets for custom dashboards

The same numbers are available as widgets under Dashboards:

They read from the same source as the Overview tab, so the two can't disagree. They only appear in the widget catalog if you hold reports:view.

Tickets: budget and fixed price

A ticket can now carry an hour budget agreed with the customer and be marked as fixed price. Both live in the ticket properties (hidden from customers, like the other billing-relevant fields).

1. Open the ticket and switch to Properties
2. Enter the agreed hours under Budget — e.g. 8h or 1d 4h
3. Turn on the Fixed price toggle

If no budget is set, the estimate is used instead — so you don't have to maintain the same number twice.

What the fixed-price toggle does: every hour beyond the budget is automatically marked not billable, and pushed to MOCO that way. In detail:

• Time entries are counted against the budget in booking order. The entry that crosses the line is split: the part that still fits stays billable, the remainder becomes its own entry right behind it and is not billable. Everything booked after that is fully non-billable.
• Entries already invoiced in MOCO are never re-flagged. They do count against the budget.
• Entries you manually set to "not billable" are left alone and consume no budget.
• If you raise the budget later or turn fixed price off again, the automatically capped entries are released. Manual decisions stay as they are.

Recalculation runs when time is booked (manually and on timer stop), when MCP drafts are approved, when an entry's duration changes or it is deleted, and when the budget, the estimate or the fixed-price toggle changes. Time arriving via the MOCO webhook is left untouched — MOCO is the source of truth there.

With fixed price on and time over budget, the ticket shows right below the toggle how much was capped. The ticket's budget summary reports non-billable minutes and over-budget minutes separately.

In MOCO, the budget (hourly rate × budget hours) and the fixed-price flag are mirrored onto the ticket's project. A split booking lands as two activities — billable and non-billable cleanly separated, with no manual rework. The same now applies when you flip the billable flag by hand.

Bulk actions: more fields, more projects, more tickets at once

Create several tickets in one pass

Under Issues there's a new Multiple tickets button. In the dialog you write one line per ticket:

Rework the login form
Fix the password reset mail
Document the session timeout

List markers (- , 1. ) are stripped automatically and empty lines ignored — so a pasted list just works. The fields below — project, type, status, assignee, priority, due date — apply to every line.

Check runs a dry pass: you see per line whether it would go through, without anything being created. Up to 100 tickets per pass, titles up to 200 characters.

The bulk action toolbar can do more

On top of status, assignee, type, epic, delete and copy:

• Labels — add or remove. Deliberately not replace: across a mixed selection, "give all of these urgent" doesn't mean "urgent is now the only label".
• Set or clear priority
• Set or clear the due date
• Archive
• Move to project — across project boundaries too

A move always asks for confirmation, regardless of count: the tickets get new ticket keys and land in the target project's backlog. Type and milestone survive only if they exist there as well. Other bulk changes ask above 50 selected tickets. The limit stays at 500 tickets per action.

A selection may now span tickets from several projects — permissions are checked per ticket and failures reported per ticket, instead of aborting the whole pass.

Bulk changes now behave like single edits

This is the change with the biggest day-to-day effect: a bulk change now takes exactly the same path as N individual edits. That means it fires notifications, activity entries, automations and live updates — it previously did not, and your colleagues' boards stayed stale after a bulk action.

So if you regularly reshuffle large selections: your automations now apply there too, and watchers get the corresponding notifications.

In short

• Dashboard: four buckets (Waiting on you, In flight, Stuck, To record) instead of fourteen sections, every ticket in exactly one place, reason chips under "Stuck", a My work / Oversight toggle for project owners. Your choice and collapsed buckets are remembered.
• Notifications: new default tab Important, the bell badge counts only important items, recurring reminders collapse into one row with a counter, snooze right in the list — and snoozing now applies to every informative type.
• Overview (new): throughput, lead time, on-time delivery, overdue, reopen rate, WIP by status with age and team load — behind the new reports:view permission (Administrators only by default). Plus four new widgets for custom dashboards.
• Tickets: Budget in hours plus a Fixed price toggle — hours over budget become non-billable automatically, the entry on the boundary is split, and MOCO is updated to match.
• Bulk actions: create multiple tickets at once (up to 100, with a dry run), plus labels, priority, due date, archive and move to another project; selections across projects; bulk changes now trigger notifications and automations.