Skip to content

GitLab Next

    • 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
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

GitLab 15.0 is launching on May 22! This version brings many exciting improvements, but also removes deprecated features and introduces breaking changes that may impact your workflow. To see what is being deprecated and removed, please visit Breaking changes in 15.0 and Deprecations.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !8266
The source project of this merge request has been removed.
Merged
Created Dec 22, 2016 by Bob Van Landuyt@reprazent🔶Maintainer14 of 15 tasks completed14/15 tasks

Create a new issue for a single discussion

  • Overview 143
  • Changes 41

What does this MR do?

Based on what is shown in #25515 (moved) I want to make it possible to create a new Issue for a single discussion in a merge request.

It also adds a button to resolve all discussions mentioned in https://gitlab.com/gitlab-org/gitlab-ce/issues/23589#note_18864573

  • Add a button to resolve a single discussion to the merge request view
  • Pre-fill a new issue when passing a a discussion to resolve
  • Resolve the discussion when creating the issue
  • Add a system note to the discussion mentioning the new issue
  • Hide the button after the issue was resolved
  • Add button to resolve all discussions in an MR

Why was this MR needed?

This is the backend part that is required to complete #25515 (moved).

Screenshots (if relevant)

The warning on the new-issue form looks like this for all discussions in an MR:

Screen_Shot_2017-02-27_at_17.29.04

And like this for a single discussion:

Screen_Shot_2017-02-27_at_17.31.34

There's a new button to create a new issue for a single discussion:

Screen_Shot_2017-01-23_at_22.45.05

And there is a button to delegate all discussions in a merge request

Screen_Shot_2017-03-08_at_20.50.58

After the issue is created, this is mentioned in a flash message:

Screen_Shot_2017-03-08_at_20.18.21

Does this MR meet the acceptance criteria?

  • Changelog entry added
  • Documentation created/updated
  • API support added
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Branch has no merge conflicts with master (if it does - rebase it please)
  • Squashed related commits together

What are the relevant issue numbers?

#25515 (moved)

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 25515-delegate-single-discussion-to-new-issue