Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,932
    • Issues 34,932
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,253
    • Merge Requests 1,253
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #8767

Closed
Open
Opened Dec 07, 2018 by Victor Wu@victorwuContributor

Issue types: User story, test case, requirement, vulnerability

Introduce issue types, so that we can independently build functionality in GitLab for each scenario, but still retain the baseline issue concept.

Issue types:

  • User story: The default issue type. This is the default type of an issue when it is first created.
  • Test case: To serve the needs of https://gitlab.com/gitlab-org/gitlab-ee/issues/8766.
  • Requirement: To serve requirements management (some issues). Parent child issue relationships (&543) should be built with the use cases of requirements management in mind. In addition, requirements, unlike user stories, are long-lasting, that reflect the current business logic/functionality of a product. So requirements would de-emphasize the open/closed statuses of issues, because requirements shouldn't be closed. They are never "done".
  • Vulnerability: To serve the needs of https://gitlab.com/gitlab-org/gitlab-ee/issues/8493.

The idea is that each issue type would extend the basic issue type (user story) with additional fields and logic in GitLab.

Edited Dec 14, 2018 by Victor Wu
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#8767