Skip to content
Snippets Groups Projects

Issues with due dates in the past "yell" in red on Epic screen, even when they are closed

    • Closed Issue created by Chase Kimball @ckimball

    Summary

    Issues related to an epic appear with red due dates, even when they are closed.

    Steps to reproduce

    • Create an issue, set its due date to the past
    • Associate it with an epic
    • Close the issue
    • On the epic screen, you will see the related issue is still "yelling" in red about its past due date

    Example Project

    https://gitlab.com/groups/rebelliondefense/-/epics/27

    What is the current bug behavior?

    Due date appears in red, even when issue is closed.

    What is the expected correct behavior?

    Due date should appear neutral, or the whole issue should be "crossed out" because it is closed.

    Relevant logs and/or screenshots

    image

    Output of checks

    (If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

    Results of GitLab environment info

    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

    (If you can, link to the line of code that might be responsible for the problem)

    Designs

      Child items ...

      2. Activity

      Please register or sign in to reply