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,512
    • Issues 39,512
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,222
    • Merge requests 1,222
  • 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
  • #255309

Closed
Open
Created Sep 24, 2020 by Raimund Hook@stingrayzaContributor

Epic API - unable to set 'created_at', 'updated_at'

Problem to solve

The Epic API currently does not allow you to set created_at or updated_at fields, although the fields do exist in replies from the API endpoint.

Proposal

Add created_at and/or updated_at fields to the list of fields that can be set upon creation or modification of an epic through the API. This would increase consistency between the Epics API and the Issues API.

Links / references

https://docs.gitlab.com/ee/api/epics.html

Edited Sep 24, 2020 by Raimund Hook
Assignee
Assign to
Time tracking