Skip to content

feat(frontend): pin frequently used pipelines #14984

Open
Open
feat(frontend): pin frequently used pipelines#14984

Description

@jeffspahr
jeffspahr
opened on Oct 20, 2026

Pipeline users need a quick way to return to pipelines they choose without repeatedly searching a long registry. Follow-up to #14584.

Implement explicit user-managed pins, with an accessible pin/unpin action and a clear pinned view. Keep ordinary list sorting predictable; do not silently rank pipelines by inferred usage. Recently viewed pipelines can be a separate optional shortcut.

Acceptance criteria:

  • Persist pins per user and workspace/namespace; define behavior for single-user deployments and shared pipelines.
  • Preserve authorization: a pin grants no access, and deleted or inaccessible pipelines are handled without leaking metadata.
  • Support keyboard interaction and explicit empty/error states.
  • Test persistence, namespace changes, deleted pipelines, and single/multi-user deployment behavior.

Decide the storage contract before implementation; browser-only preferences should be clearly scoped to that browser. This feature is outside the UI modernization merge scope.

Activity

  1. github-actions commented on Oct 20, 2026

    @github-actions
    github-actionsBot
    on Oct 20, 2026 – with GitHub Actions

    🤖 AI Issue Quality Review

    📊 Scope

    • Feature boundary is clear: explicit pin/unpin plus a pinned view, with no inferred ranking.
    • No specific files, components, or packages are named; the storage layer (frontend-only vs. backend API) is left open.

    📝 Context & Guidance

    ⚡ Complexity

    • Medium to High.
    • It spans UI, persistence, per-namespace and per-user semantics, authorization, and single/multi-user modes. A backend change is possible depending on the storage decision.

    🎯 Overall Issue Quality Verdict

    • Not ready for immediate pickup, because the storage decision is a blocker.
    • Most impactful recommendation: settle the storage contract (browser-local vs. server-side) in the issue or a short design note, and list the affected frontend files.

    Generated by AI issue quality analyzer for #14984 · copilot · auto · 5.26 AIC · ⌖ 0.475 AIC · ⊞ 5.8K · ◷

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions