You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a PM or Admin, I want to filter the Knowledge Base artifact list for GitHub organization-level metadata (org profile, teams, and members), so that I can inspect an organization's structure and people separately from repository content like commits, issues, and pull requests.
The backend already delivers ORG_METADATA artifacts, but the frontend's ArtifactType union and the Knowledge Base tab bar (ALL | UPLOADS | PR | ISSUES | FILES | COMMITS) don't know the type. Org artifacts therefore render under "All" without a dedicated icon, label, or way to isolate them.
In Scope
New "Organization" filter tab in the Knowledge Base artifact filter bar
Extend the frontend ArtifactType union with ORG_METADATA (type mapping, icon, display name)
Org-aware rendering in the artifact viewer drawer (org profile: description, location, blog, repo counts; teams and members from artifact metadata)
Acceptance Criteria
A filter tab "Organization" appears alongside the existing tabs and shows only GitHub ORG_METADATA artifacts when active.
Org artifacts have a dedicated icon and display the organization name (not a generic/unknown label) in the artifact list.
The artifact viewer drawer renders the org profile (description, location, blog, public/private repo counts) and lists teams and members from the artifact metadata.
The filter combines correctly with the text search and pagination (same behavior as the existing tabs).
Empty state when no org metadata has been ingested for the selected project.
i18n (en/de), light/dark themes, keyboard-accessible tab bar (existing ArtifactFilters behavior).
Unit tests for the filter logic (useKnowledgeBase) and the ORG_METADATA type mapping.
User Story
As a PM or Admin, I want to filter the Knowledge Base artifact list for GitHub organization-level metadata (org profile, teams, and members), so that I can inspect an organization's structure and people separately from repository content like commits, issues, and pull requests.
Context & Motivation
team:frontend(primary)ORG_METADATAartifact per connected org, with teams and members in its artifact metadata).The backend already delivers
ORG_METADATAartifacts, but the frontend'sArtifactTypeunion and the Knowledge Base tab bar (ALL | UPLOADS | PR | ISSUES | FILES | COMMITS) don't know the type. Org artifacts therefore render under "All" without a dedicated icon, label, or way to isolate them.In Scope
ArtifactTypeunion withORG_METADATA(type mapping, icon, display name)Acceptance Criteria
ORG_METADATAartifacts when active.ArtifactFiltersbehavior).useKnowledgeBase) and theORG_METADATAtype mapping.Technical Notes
src/features/knowledge-base/tabs.ts(TABS,KnowledgeTab),useKnowledgeBase.ts(tab matching),types.ts(ArtifactType),ArtifactViewerDrawer.tsx, icon mapping.ORG_METADATAis already served by the artifact endpoints.ORGANIZATION/TEAM/MEMBERartifact types, as visioned in [Story]: Ingest GitHub organization-level metadata (org profile, members, teams) #261) are out of scope here — the current backend persists one org artifact; splitting it is backend work tracked in [Story]: Ingest GitHub organization-level metadata (org profile, members, teams) #261.Sub-Tasks (by team)
ArtifactType+ tabs + filter logic, org icon/label, viewer drawer rendering, i18n, unit tests.