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 FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 1,668
    • Issues 1,668
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 487
    • Merge requests 487
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • 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
  • GitLab FOSSGitLab FOSS
  • Issues
  • #33264
Closed (moved) (moved)
Open
Issue created Jun 02, 2017 by Victor Wu@victorwuReporter

Merge request UI implies protected branches and forked branches can be deleted

Problem

Protected branches cannot be deleted: https://docs.gitlab.com/ce/user/project/protected_branches.html. Currently, when you create a merge request, you have the option to select removing a branch. This option should not appear anywhere in the merge request create/edit web form, and should not appear in the merge request widget. As shown in the screenshot, there is a disabled checkbox with the label in the widget. Currently, when you merge the merge request, it does not delete the branch. This is correct. But the UI is misleading. This should be corrected.

img

Similarly, for a merge request where the source branch is a fork, the author can toggle removing the source branch in the edit web form of the merge request. However, in the widget itself, the maintainer of the master branch cannot change the checkbox because it is disabled. In this case, it is confusing to see an empty checkbox.

img

Design

Edit/create merge request screen

User does not have permissions
  • Don't show option at all. Don't show the checkbox. Don't show the text label. Show nothing.

  • We don't have to show anything all because the user will see anything (if they need to), later on the widget itself.

User does have permissions
  • [CHECKBOX] Remove source branch

Merge request widget

User does not have permissions
  • Merging will not remove the source branch. Therefore, show nothing at all.

MR-merged-environment-performance-1_Copy_31

  • Merging will remove the source branch.

MR-merged-environment-performance-1_Copy_29

MR-merged-environment-performance-1_Copy_37

User does have permissions
  • [CHECKBOX] Remove source branch

MR-merged-environment-performance-1_Copy_35

MR-merged-environment-performance-1_Copy_33

Edited Aug 18, 2017 by Victor Wu
Assignee
Assign to
Time tracking