Birdhouse

Data freshness

Data & sync

Next scheduled sync: unknown Open Data & sync

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—

Set up on a laptop

These tasks put long project names beside each other, use multi-select fields, and search a Jira board directory. That does not fit a phone, and we will not pretend it does.

On a larger screen, this page also has the sync log and technical connection details.

Delivery / Integrations

Integrations

Checking your data…

Loading the latest sync evidence from shared storage.

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— State—
Hours & budget use from Yoobi · feeds Dashboards, project pages, reports In Birdhouse— Updated— Next— State— Refreshes only with the scheduled Yoobi sync.
Jira sprint progress from Jira · feeds project Jira tabs, sprint reports In Birdhouse— Updated— Next— State—

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
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.