Skip to content
Snippets Groups Projects

Moving an Issue between projects in Milestone shows twice

    • Closed Issue created by Adam Markham @mountainraptor

    Summary

    Moved issues appear twice in a group level Milestone - once as Closed, and once as open. This effects metrics and milestone progress

    Steps to reproduce

    1. Create a group level milestone.
    2. Assign issues in multiple projects to that group level milestone.
    3. Move an issue from one project in that milestone to another
    4. See issue appear twice in milestone (once closed, and once in the expected state).

    Example Project

    What is the current bug behavior?

    Issues appear twice in a Milestone.

    What is the expected correct behavior?

    Moved issues only appear once in the Milestone.

    Relevant logs and/or screenshots

    Output of checks

    Results of GitLab environment info

    gitlab.com

    Expand for output related to GitLab environment info 
    (For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

    Results of GitLab application Check

    Expand for output related to the GitLab application check 
    (For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
    

    (For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
    

    (we will only investigate if the tests are passing)

    Possible fixes

    Designs

    Child items ...

    • Activity

    Please register or sign in to reply