Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !14016

Merged
Created Sep 03, 2017 by Hiroyuki Sato@hiroponz🇯🇵Contributor4 of 11 tasks completed4/11 tasks

Add my_reaction_emoji param to /issues and /merge_requests API

  • Overview 10
  • Commits 3
  • Pipelines 7
  • Changes 9

What does this MR do?

Follow-up from "Add filter by my reaction" (!12962 (merged))

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

No.

Why was this MR needed?

It is need to be consistent with the issues/merge requests filter feature.

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • Documentation created/updated
  • API support added
  • Tests added for this feature/bug
  • Review
    • Has been reviewed by UX
    • Has been reviewed by Frontend
    • Has been reviewed by Backend
    • Has been reviewed by Database
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together

What are the relevant issue numbers?

Nothing.

Edited Sep 04, 2017 by Hiroyuki Sato
Assignee
Assign to
Reviewer
Request review from
10.0
Milestone
10.0 (Past due)
Assign milestone
Time tracking
Source branch: issue-api-my-reaction