Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • 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 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #13216
Closed
Open
Issue created Aug 01, 2019 by Virjinia Alexieva@valexievaContributor

Implement a date picker for cycle analytics

Problem to solve

Currently users cannot select a specific date for customizable cycle analytics, which means that they cannot drill down in productivity during a specific sprint since we only provide last 7, 30 days, etc as periods.

Intended users

EMs, PMs, Tech leadership

Further details

Proposal

I would recommend adding a date picker to cycle analytics page, where currently the custom ranges are, similar to the spec in productivity analytics.

Backend

With customizable stages, we will be able to scope the calculation between a date range. TODO: sync with FE about the param naming.

Permissions and Security

Same permissioning as on the overall page

Documentation

Testing

What does success look like, and how can we measure that?

A user should be able to select any period for which they have data and load it within [5] seconds

What is the type of buyer?

Links / references

Edited Aug 02, 2019 by Adam Hegyi
Assignee
Assign to
Time tracking