Going to repurpose this epic to contain the issues necessary to get to the goal of creating and displaying work items that are scoped to the group level. Part of this work is creating the Epic work item type, but the work to migrate or link the legacy epic to the epic work item type will occur in the future. <details><summary>Previous description</summary> ## Product Goals - There is no difference between the issue/work item experience at the group or project level - Issues/work items can live natively within a group without needing a child project. - Default to "on" ASAP. ## Frontend Goals - Remove duplication and any specialized group/project-specific code. - Group and projects use the same frontend Vue apps + APIs for the list, board, and bulk update, ... - Issue-related settings for groups and projects should be consolidated into a single implementation that powers both group and project issue-related settings. - 1-1 parity between groups and projects for issue (and work item) related interfaces backed by using `namespace` as the foundation. ## Known inconsistencies - Group settings do not contain the necessary settings for natively managing issues. - Groups don't have repos. - Bulk-update settings are different between group and project. - CSV import/export missing from Group. - Import from Jira + Jira integration missing from groups (I think) - Need to default to `self` for the target to create new work items / issues within. Allow selecting alternative parent/children. - Some board inconsistencies between group/project. - Move needs to support all namespaces. - Clone needs to support all namespaces. - When in a parent namespace, need a way to define which child project to create an MR/branch in from an issue/work item in the parent namespace. - ...probably a lot more edge cases :smile: ## Iteration Path Moved to the parent epic's description > https://gitlab.com/groups/gitlab-org/-/epics/8308#iteration-path </details>