Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,894
    • Issues 34,894
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,221
    • Merge Requests 1,221
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #13188

Closed
Open
Opened Jul 31, 2019 by Virjinia Alexieva@valexievaContributor

Implement a date picker for productivity analytics

Problem to solve

Currently users cannot select a specific date for productivity 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

  1. I would recommend adding a date picker to productivity analytics page as per the below screenshot

image-4

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 Sep 27, 2019 by Virjinia Alexieva
Assignee
Assign to
12.4
Milestone
12.4 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#13188