Skip to content
Snippets Groups Projects
New issue look: Off

Issues Lose Association to Closed Milestones

    • Closed Issue created by username-removed-20308 @rickg421

    I think the root of the problem is that closed milestones are not eligible to receive issue assignment. My steps to reproduce:

    1. Create new milestone Test Milestone
    2. Create new issue Test Issue against Milestone
    3. Close Test Milestone

    At this point, the milestone will still show the issue as assigned. If you were to view the issue itself, it would show no milestone assigned. Everything is still OK at this point, although there's a minor UI issue of not showing the assigned milestone when that milestone is closed.

    1. Edit the issue (e.g. subject line)

    Because the milestone field is unpopulated, this "empty" value is stored as the milestone assignment and thus the issue is disassociated from the milestone. This causes a loss in history for tracking when issues were resolved.

    I think it would correct to say that only open milestones -or- currently assigned milestone are eligible for issue assignment.

    System Information

    System information
System:         Debian 7.5
Current User:   git
Using RVM:      no
Ruby Version:   2.0.0p353
Gem Version:    2.0.14
Bundler Version:1.5.1
Rake Version:   10.3.1
Sidekiq Version:2.17.0

GitLab information
Version:        6.9.2
Revision:       e46b644
Directory:      /home/git/gitlab
DB Adapter:     mysql2
URL:            http://example.com
HTTP Clone URL: http://example.com/some-project.git
SSH Clone URL:  git@example.com:some-project.git
Using LDAP:     no
Using Omniauth: no

GitLab Shell
Version:        1.9.4
Repositories:   /home/git/repositories/
Hooks:          /home/git/gitlab-shell/hooks/
Git:            /usr/bin/git

    Designs

    Child items ...

    • Activity

    Please register or sign in to reply