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
  • Sign up now
  • 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 has launched! Please visit Breaking changes in 15.0 and 15.0 Removals to see which breaking changes may impact your workflow.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !13335
The source project of this merge request has been removed.

Add time stats to Issue and Merge Request API

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Travis Miller requested to merge travismiller/gitlab-ce.1:28453-add-time-estimate-time-spent-to-api-issue-output into master Aug 07, 2017
  • Overview 34
  • Commits 6
  • Changes 9

What does this MR do?

Adds time stats to API::Entities::IssueBasic and API::Entities::MergeRequestBasic

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

  • How much overhead does this add to the endpoints?
  • Are the appropriate issues and merge_requests endpoints indicating the correct output in the API docs?

Why was this MR needed?

Issue #28453 (closed) is tagged ~"Accepting Merge Requests"

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • Documentation created/updated
  • API support added
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • 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
  • Branch has no merge conflicts with master (if it does - rebase it please)
  • Squashed related commits together

What are the relevant issue numbers?

Closes #28453 (closed)

Edited Aug 30, 2017 by Robert Speicher
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 28453-add-time-estimate-time-spent-to-api-issue-output