Skip to content

Create an initial Backstage view for flow insights #228

@ourchitectureio

Description

@ourchitectureio

Summary

Provide an early embedded experience in an existing developer portal surface.

Why

Backstage is a strong integration surface for early adoption, but it should consume the IDP API rather than become the center of truth.

Scope

Render:

  • my blockers
  • team flow highlights
  • service-level risk signals
  • links back to GitHub or GitLab native objects

Acceptance criteria

  • View uses the IDP API rather than provider APIs directly
  • Prioritizes actionable insights over raw events
  • Handles mixed-provider scenarios cleanly
  • Includes clear loading, empty, and error states

Notes

Start with a narrow card or page. Do not let the UI drive the domain model.

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent-eligibleSuitable for autonomous AI agent processingreadyTriaged and ready for work

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions