Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 9,362
    • Issues 9,362
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 139
    • Merge requests 139
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Do not update/delete: Banner broadcast message test data

Do not update/delete: Notification broadcast message test data

  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #9749
Closed
Open
Issue created May 10, 2017 by Victor Wu@victorwuContributor

Empty states for issue lists and merge request lists

Background

Right now there are different empty states for issue lists and merge request lists for the project lists and group lists. In particular, the empty state is different if you are looking at a project with no issues, and if you are searching a project list but return zero results.

This is unnecessarily confusing and complicates the product (and thus the code). Let's simplify to improve stability and avoid situations such as: https://gitlab.com/gitlab-org/gitlab-ce/issues/31384.

I.e. we should not maintain these separate existing designs. They should merge into the same design.

Description

  • A simple design to streamline everything into a single empty state.
  • When you go to any issue (or mr) list, you always see the search bar (or filter dropdowns for group lists), even if there is nothing to show. There is an empty state message, there is a call-to-action (a button) to create a new issue (or merge request). And there is the email a new issue to this project (if it is a project list view).
  • When you search an issue (or mr) list (or filter for group lists), and you get no results, you get the identical empty state with the message, call-to-action, and the email link (if applicable).
  • In the case of the group list, the call-to-action button is a dropdown that lets you select a project.
Assignee
Assign to
Time tracking