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
  • #196066
Closed
Open
Issue 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
Time tracking