Empty state for work items planning view page

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

When no work items exist for a namespace, we should include empty state messaging that describes work items with a clear action to get started.

Proposal

Note

This mostly follows the legacy list empty state behavior (which recently had some updates for a more simplified experience in (#560277)), with some adjustments based on the new Consolidated List and leveraging the create modal.

Only show the primary empty state message in the case no items exist (either open or closed). For example, if items exist but they are all closed, show the general No results found message that we show based on no results due to filters.

Illustration: empty-issues-add-md

Heading: Track bugs, plan features, and organize your efforts with work items

Subtext: Use work items (also known as tickets or stories on other platforms) to collaborate on ideas, solve problems, and plan your project.

Scenarios

Project Level

• Present the user with the action "New item", which opens the create modal.
  • No Group/project selector is shown, as we only allow creating within this namespace.
  • Default Type to Issue

Group Level (No Projects exist && using Free version)

• Present the user with the action "New project", which upon selecting would start the Create new project flow within that namespace ([namespace] / New project)

Group Level (Projects exist && using Free version)

• Present the user with the action "New item", which opens the create modal.
  • Default the Project selector to the first project available in the list.
  • Default Type to Issue

Group Level (Premium + version – doesn't matter if projects exist or not)

• Present the user with the action "New item", which opens the create modal.
  • Default the Group/Project selector to the current namespace/group.
  • Default Type to Epic