Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #9967

Closed
Open
Created Jan 12, 2016 by Administrator@rootOwner

MRs created from UI and API are different

Created by: klausbayrhammer

When creating a merge request with an empty description the behavior is different whether this is done via the gitlab UI or the REST-API.

If I create the MR via the UI and query https://gitlab.com/api/v3/projects/1/merge_request/1?private_token=xxxx the description is an empty string. If I create the MR via the REST-API and do not set the description param e.g.

 curl -X POST --data-urlencode "source_branch=$currentBranch" \
        --data-urlencode "target_branch=master" \
    --data-urlencode "title=$lastCommitsSubject" \
    --data-urlencode "private_token=$privateToken" \
    https://gitlab.com/api/v3/projects/$projectId/merge_requests

and query the MR with https://gitlab.com/api/v3/projects/1/merge_request/1?private_token=xxxx the description is null.

It would be nice if the behavior would be the same in both cases - since this also causes problems in jenkinsci/gitlab-plugin#179

Gitlab version: Gitlab 8.2.2-ee

Assignee
Assign to
Time tracking