Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 39,511
    • Issues 39,511
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,221
    • Merge requests 1,221
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #26911

You need to sign in or sign up before continuing.
Closed
Open
Created Feb 22, 2019 by Mark Fletcher@markglenfletcher🔴Maintainer

API: `merged_at` values missing for certain Merge Requests in `merged` state

Summary

In gitlab-insights and future features we rely on the merged_at timestamp being available for Merge Requests in the merged state. Under certain circumstances this field isn't available for merged MRs when indexing MRs and retrieving and individual MR via the API.

This definitely does not affect all MRs, but I could not notice a pattern between those affected

Steps to reproduce

  • Query api/v4/projects/:project_id/merge_requests
  • Notice some MRs do not have merged_at data available

Example Project

The following merged MR is an example that exhibits the problem:

  • https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24137
  • https://gitlab.com/api/v4/projects/gitlab-org%2Fgitlab-ce/merge_requests/24137

What is the current bug behavior?

  • merged_at field is null

What is the expected correct behavior?

  • merged_at field should be populated with the relevant timestamp

Relevant logs and/or screenshots

N/A

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

gitlab-ce~3293941 v11.8.0-rc9

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited Nov 02, 2020 by Dan Jensen
Assignee
Assign to
Time tracking