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
  • !9530
Merged
Created Feb 25, 2017 by Timothy Andrew@timothyandrewContributor36 of 39 tasks completed36/39 tasks
  • Review changes

  • Download
  • Email patches
  • Plain diff

API routes referencing a specific issue should use the issue `iid`

  • Overview 13
  • Commits 8
  • Pipelines 13
  • Changes 26

What does this MR do?

  • Use Issues and MR iids instead of id for API v4 routes of the form /projects/:project_id/issues/:issue_id

Are there points in the code the reviewer needs to double check?

  • Make sure there aren't any endpoints that need to be migrated to IID that aren't covered by this MR.
  • Make sure v3 compatibility is maintained.

Why was this MR needed?

  • This change makes the API more closely resemble the routes of the web interface.
  • Since this is a breaking change, this should go into API v4.

Tasks

  • Implementation
    • Modify routes in lib/api/issues
    • Modify routes in lib/api/merge_requests
    • Any other instances of :merge_request_id
      • Merge request diffs
      • Award emoji
      • Todos API
      • TimeTrackingEndpoints
    • Any other instances of :issue_id
      • Award emoji
      • Todos API
      • TimeTrackingEndpoints
  • Tests
    • Added
    • Passing
  • Meta
    • CHANGELOG entry created
    • Branch has no merge conflicts with master
    • Squashed related commits together
    • Added screenshots
    • Check for clean merge with EE
    • Documentation added/updated
      • Merge requests API
      • Issues API
      • Award emoji API
      • Todos API
      • Time tracking endpoints
      • Update v3-to-v4 document
  • Follow-up
    • Sanity check from command line
    • Verify that V3 API is unaffected
      • Backport "time tracking endpoints" to v3
      • Any other V3 backports to be made?
    • Verify that award emoji conflict was resolved correctly
    • Verify that conflicts on EE branch were resolved correctly
  • Review
    • Reviewer
    • Maintainer
  • Wait for merge

  • Closes #28251 (closed)
  • Related EE MR: gitlab-org/gitlab-ee!1325
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 28251-mr-and-issue-iids-for-api-v4