UI: Scope tag suggestions to current flow/deployment and add Tags filter on Deployment Runs tab

[zzstoatzz]

This discussion was created from a Slack thread conversation.

Original Thread: https://prefect-community.slack.com/archives/C04DZJC94DC/p1764162696323909

---

Context
Users with multiple flows/deployments use run tags for categorization (e.g., run-type, tenant, cluster). In Prefect 3.x UI, when viewing a specific deployment’s Runs tab, there is no Tags filter, and where a tags selector does exist (e.g., dashboard cards), tag suggestions are sourced from recent runs across the entire workspace, not from the selected flow/deployment.

Current behavior

• Deployment Details → Runs tab: only state/name filters are shown; no tags filter is available.
• Tags suggestions (e.g., in dashboard Flow Runs card) are built from a workspace-wide sample of recent runs, so suggestions include tags unrelated to the current flow/deployment.
• Backend supports the needed scoping via filters (FlowRunFilterTags + DeploymentFilter), but the UI does not expose a tags filter on the deployment runs view, nor scope tag suggestions to the current selection.

Evidence

• Filters API supports the combination needed:
  • FlowRunFilterTags / FlowRunFilterDeploymentId
  • DeploymentFilter (by id)
    Docs: https://docs.prefect.io/v3/api-ref/python/prefect-server-schemas-filters/
• REST API for flow runs supports the same combination in /api/ui/flow_runs/history
  Docs: https://docs.prefect.io/v3/api-ref/rest-api/server/flow-runs/

Problem

• Users with many tags across different flows see noisy/unrelated tag suggestions, and cannot filter by tags directly within the Deployment Runs context.
• This makes it harder to answer simple questions like: “Show only runs of this deployment that have tag X”.

Requested enhancements

1. Add a Tags filter to the Deployment Details → Runs tab.
2. Scope tag suggestions to the current context:
   • When viewing a flow: suggest tags observed on runs of that flow.
   • When viewing a deployment: suggest tags observed on runs of that deployment.
   • Optionally allow “All workspace tags” as a secondary mode.

Acceptance criteria

• A Tags control appears on the deployment’s Runs tab alongside existing filters (state, search, etc.).
• Tag suggestions default to tags present on runs for the selected deployment (or flow), not workspace-wide.
• Users can type arbitrary tags that may not be in suggestions (to match current freeform behavior).
• Filters can be persisted via Saved Searches.

Workarounds today

• Use the global Runs view and add filters: Deployment = + Tags = <typed tag(s)>, then save as a Saved Search.
• Programmatically query via client with FlowRunFilter(tags=...) + DeploymentFilter(id=...).

Rationale / Impact

• Reduces noise and improves discoverability of relevant tags.
• Aligns the UI with backend capabilities.
• Improves productivity for users with many teams/flows sharing a workspace.

If helpful, we can provide additional screenshots or a short Loom showing current behavior vs desired.

---

This discussion was automatically created by the Marvin bot to preserve valuable community insights.