GitLab — Issue browser

Tables & ListsSee it livegitlab.com

A work-item list uses colorful labels, owners and metadata to keep many issues scannable in a compact space.

GitLab — Issue browser — captured interface — Viewport capture · opening screen

Source capture · 2026-09-08Open full image ↗

Why this pattern works

A work-item list uses colorful labels, owners and metadata to keep many issues scannable in a compact space.

Design notes

Surface: GitLab — Issue browser
Navigation: Application sidebar beside search controls and tightly stacked issue rows.
Layout: Application sidebar beside search controls and tightly stacked issue rows.
Density: Compact supporting controls preserve space for the primary content.
Color: White, light gray and multicolored status labels
Type: Clear sans-serif labels with stronger section headings and smaller metadata.
Pattern: A work-item list uses colorful labels, owners and metadata to keep many issues scannable in a compact space.
States: Public opening screen as captured; subsequent actions and authenticated states were not tested.
Don't: Use the structure as a reference, with your own content and identity. This still does not establish the behavior of controls or unseen states.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: GitLab — Issue browser
Source: https://gitlab.com/gitlab-org/gitlab/-/work_items
Swipefile reference: https://swipefile.design/ref/expand-gitlab-issue-browser/
Captured: 2026-09-08. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: GitLab — Issue browser
- nav: Application sidebar beside search controls and tightly stacked issue rows.
- layout: Application sidebar beside search controls and tightly stacked issue rows.
- density: Compact supporting controls preserve space for the primary content.
- color: White, light gray and multicolored status labels
- typography: Clear sans-serif labels with stronger section headings and smaller metadata.
- pattern: A work-item list uses colorful labels, owners and metadata to keep many issues scannable in a compact space.
- states: Public opening screen as captured; subsequent actions and authenticated states were not tested.
- dont: Use the structure as a reference, with your own content and identity. This still does not establish the behavior of controls or unseen states.

Useful for: A work-item list uses colorful labels, owners and metadata to keep many issues scannable in a compact space.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: A work-item list uses colorful labels, owners and metadata to keep many issues scannable in a compact space.

GitLab — Issue browser

Make it your own

Keep exploring

Help improve Swipefile?