feat(dashboards): add DashboardWidget model and table migration (1/11)

[MattPua]

Problem

Dashboard widgets need a first-class persisted entity (DashboardWidget) separate from insights and text tiles. This stack starts with schema-only changes so each migration can ship and deploy independently.

This PR is 1/10 in the dashboard widgets Graphite stack (migration foundation).

Changes

• Add DashboardWidget model (products/dashboards/backend/models/dashboard_widget.py)
• Migration 0007_dashboardwidget_table — creates posthog_dashboardwidget (new table only, no locks on existing dashboard tables)
• Wire model into products/dashboards/backend/models/__init__.py

How did you test this code?

• Agent: did not run manual migrations locally
• hogli test products/dashboards/backend/ — not run on this slice alone; migration is additive-only

👉 Stay up-to-date with PostHog coding conventions for a smoother review.

Publish to changelog?

no

Docs update

skip-inkeep-docs (internal schema prep)

🤖 Agent context

• Agent-assisted split of the dashboard-widget-foundation WIP branch into a 10-PR Graphite stack for safer review and deploy
• Lock-risk migrations are isolated into separate PRs (this one is low risk: new table only)
• No product behavior change until later stack PRs

[MattPua]

• feat(dashboards): add widget registry, run_widgets, and dashboard widget API (6/11) #60494 : 2 dependent PRs (#60495 , #60523 )
• feat(dashboards): add concurrent indexes for dashboard widget tiles (5/11) #60493
• feat(dashboards): validate dashboard tile widget constraints (4/11) #60492
• feat(dashboards): extend dashboard tile exclusivity check for widgets (3/11) #60491
• feat(dashboards): add dashboard tile widget_id column (2/11) #60490
• feat(dashboards): add DashboardWidget model and table migration (1/11) #60489 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Greptile encountered an error while reviewing this PR. Please reach out to support@greptile.com for assistance.

[github-actions]

Migration SQL Changes

Hey 👋, we've detected some migrations on this PR. Here's the SQL output for each migration, make sure they make sense:

products/dashboards/backend/migrations/0007_dashboardwidget_table.py

BEGIN;
--
-- Custom state/database change combination
--

                        CREATE TABLE "posthog_dashboardwidget" (
                            "id" uuid NOT NULL PRIMARY KEY,
                            "widget_type" varchar(64) NOT NULL,
                            "name" varchar(400) NULL,
                            "description" text NOT NULL,
                            "config" jsonb NOT NULL,
                            "last_modified_at" timestamp with time zone NOT NULL,
                            "created_by_id" integer NULL REFERENCES "posthog_user" ("id") DEFERRABLE INITIALLY DEFERRED,
                            "last_modified_by_id" integer NULL REFERENCES "posthog_user" ("id") DEFERRABLE INITIALLY DEFERRED,
                            "team_id" integer NOT NULL REFERENCES "posthog_team" ("id") DEFERRABLE INITIALLY DEFERRED
                        );
                        CREATE INDEX IF NOT EXISTS "posthog_dashboardwidget_created_by_id" ON "posthog_dashboardwidget" ("created_by_id");
                        CREATE INDEX IF NOT EXISTS "posthog_dashboardwidget_last_modified_by_id" ON "posthog_dashboardwidget" ("last_modified_by_id");
                        CREATE INDEX IF NOT EXISTS "posthog_dashboardwidget_team_id" ON "posthog_dashboardwidget" ("team_id");
                    
COMMIT;

Last updated: 2026-05-28 19:01 UTC (d76dea8)

[github-actions]

🔍 Migration Risk Analysis

We've analyzed your migrations for potential risks.

Summary: 0 Safe | 1 Needs Review | 0 Blocked

⚠️ Needs Review

May have performance impact

dashboards.0007_dashboardwidget_table
  └─ #1 ✅ SeparateDatabaseAndState
     Wrapper operation - see nested operations for risk: RunSQL
     database_operations: RunSQL
     └─ #2 ⚠️ RunSQL: CREATE INDEX without CONCURRENTLY locks table

📚 How to Deploy These Changes Safely

RunSQL:

Use CONCURRENTLY to avoid table locks: CREATE INDEX CONCURRENTLY IF NOT EXISTS

Last updated: 2026-05-28 19:02 UTC (d76dea8)

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-05-29 13:55 UTC	Run
prod-us	✅ Deployed	2026-05-29 14:26 UTC	Run
prod-eu	✅ Deployed	2026-05-29 14:37 UTC	Run