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 38,034
    • Issues 38,034
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1,347
    • Merge requests 1,347
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #196066

Closed
Open
Created Jan 09, 2020 by Gabe Weaver@gweaver🌀Developer

More clearly communicate that a milestone is expired

Problem to solve

As a follow up to gitlab-com/gl-infra/delivery#610 (comment 267007310), there is currently no visual indicator when selecting a milestone whether it is expired or not. This could inadvertently lead to issues and merge requests being assigned to the incorrect or outdated milestone.

Proposal

  1. Move expired milestones to the bottom of the milestone list to discourage adding issues to expired milestones
  2. Add (expired) next to expired milestones within the milestone select field:

Drop Down

Edited Jun 24, 2020 by Gabe Weaver
Assignee
Assign to
13.4
Milestone
13.4 (Past due)
Assign milestone
Time tracking