Skip to content
Delivery Manager Birdhouse Admin session

Manage

Integrations Data & sync — read-only
Birdhouse
D Delivery Here

On the way

F Finance In build
H People In design

Switching opens a new page (~3 page loads).

Home Projects Planning Reports Client portal

Outbirds

Data freshness

Data & sync

    Next scheduled sync: unknown Open Data & sync
    Home Projects Planning Reports Portal

    Integrations

    Checking your data…

    Loading the latest sync evidence from shared storage.

    Your data

    Projects, rates & budgets—
    In Birdhouse—
    Updated—
    Next—
    Hours & budget use—
    In Birdhouse—
    Updated—
    Next—
    Jira sprint progress—
    In Birdhouse—
    Updated—
    Next—

    Needs you

    Repair and diagnostics are desktop work

    Targeted repair, board linking and Setup & diagnostics open on a computer. Bringing codes home and linking people work here — those are two-second decisions, not configuration.

    Delivery / Integrations

    Integrations

    Checking your data…

    Loading the latest sync evidence from shared storage.

    Admin only. The server calculates the current backlog duration when it queues the paced run; it overwrites, never duplicates, and leaves sent reports untouched.
    Provider sync Working
    Preparing…

    Needs you 0

    Things syncing can’t do by itself. Open a task to handle it right here.

    New Yoobi projects need a project type Untyped projects stay out of dashboards and reporting. Assign types
    Untyped project inbox clear Use active/closed filters and search to select Yoobi projects, then apply a Birdhouse type in bulk.
    Birdhouse users are not linked to a Yoobi resource Without a link their hours appear under nobody’s name. Link people

    Loading the link queue…

    A link decides under whose name Yoobi hours land in Birdhouse. Without one, someone stays empty in occupancy, My week and the resource actuals — the hours exist, they just belong to nobody.

    Linked users

    Projects without a Jira board Sprint progress can’t sync until a board is linked. Link boards
    Loading the Jira board directory…
    No Yoobi-created active projects ready for Jira mapping Provider read models load this queue after signed Yoobi/Jira sync evidence is available.
    Checking hour classification… Hours outside every bucket count as neither billable, warranty, non-billable nor internal. Classify codes

    Opens the "Hoe uren worden ingedeeld" row below, where every unmapped activity name can be given a bucket.

    Yoobi hours coverage

    Coverage unavailable: no Yoobi time-entry reconciliation has been committed. Sign in and wait for a scheduled Yoobi sync.

    • complete — no action
    • incomplete or never fetched — a button, click to repair
    • before the start date
    • the rest of this year — not due yet
    At least ± 11 min, paced · the total duration is not measured.

    Yoobi history

    Targeted repair

    Only the selected months are requested. Sent reports are untouched.

    Overwrites, does not duplicate. Sent reports are untouched.

    Your data

    Where each number in Delivery comes from, how much of it we hold, and how fresh it is. Times are Amsterdam.

    Projects, rates & budgets from Yoobi · feeds Projects and budget columns In Birdhouse— Updated— Next— —
    Hours & budget use from Yoobi · feeds Dashboards, project pages, reports In Birdhouse— Updated— Next— — Refreshes only with the scheduled Yoobi sync.
    Jira sprint progress from Jira · feeds project Jira tabs, sprint reports In Birdhouse— Updated— Next— —

    Sync log

    Every automatic and manual sync, newest first, with exactly what it moved. Successful hourly Jira refreshes are grouped per day; click a run for the full breakdown.

    Loading sync history…

    Unmapped Yoobi codes

    Actual hours whose Yoobi project code does not match a current Delivery project. They remain outside the project portfolio until the source project is available.

    Checking the latest Yoobi hours sync…

    Refresh Yoobi projects to retry matching against the current source inventory.

    Setup & diagnostics

    Connections, credentials and technical detail Checking production config
    Reads configuration state only; no secret values are returned.
    • Supabase productionChecking configuration.
    • Yoobi v2Checking configuration.
    • Jira CloudChecking configuration.
    • Sync runnerChecking configuration.
    • Inngest schedulerChecking configuration.
    • Sentry observabilityChecking configuration.
    Requires signed-in Delivery access and production Yoobi credentials.
    Requires signed-in Delivery access and production Jira credentials.
    Signed-in preview compares Yoobi project-code inventory with current Birdhouse Delivery projects without provider writes.
    Signed-in Delivery access refreshes the sanitized Jira board-code directory for project mapping.
    Technical details — per-dataset commit evidence
    Sync evidence Waiting
    Sign in to load shared production read-model evidence; first paint shows local browser state.
    • Yoobi projects, resources, rates, budgets, and activities Missing No live commit loaded · Waiting for first committed read model yoobi / projects_resources_rates_budgets_activities / twice daily
    • Yoobi time entries and actual hours Missing No live commit loaded · Waiting for first committed read model yoobi / actual_hours_billability_and_warranty / twice daily
    • Jira board directory Missing No live commit loaded · Waiting for first committed read model jira / board_code_directory / hourly
    • Jira board progress Missing No live commit loaded · Waiting for first committed read model jira / issue_epic_sprint_project_progress / hourly
    • Delivery report SLA projection Missing No live commit loaded · Waiting for first committed read model birdhouse / report_due_overdue_and_send_state / hourly
    • Jira support board tickets Missing No live commit loaded · Waiting for first committed read model jira / service_desk_tickets / hourly
    How hours are classified Opens to calculate
    Twelve-month hour totals and project counts per Yoobi activity name. Only administrators can change a bucket; the classifier everyone's reports use consults this mapping first.

    Yoobi activity Bucket Hours · 12 mo Projects

    Threshold settings

    Firm-wide. Applies to every planning, utilisation and warranty view in Delivery. Only administrators can change these values; everyone sees which value applies.

    Capacity — per resource per week

    Warranty — share of delivered hours

    Birdhouse go-live — history boundary

    Report periods that ended before this date count as history: they never turn red and stay out of the SLA figures. Booked hours keep being measured in full.

    Standaard — nog niet gewijzigd.

    Something not right?

    If a figure does not match Yoobi or Jira, ask an administrator to run a full sync. Say which project and which figure, so nobody has to go looking.