locking issue hides open/closed status

Summary

Locking an issue hides open/closed status

Steps to reproduce

Lock a closed issue

Example Project

gitlab-design#185 (moved)

What is the current bug behavior?

When locking the issue, the open/closed status is not visible anymore

What is the expected correct behavior?

You should still be able to see the open/closed status

ref: https://gitlab.slack.com/archives/C03MSG8B7/p1542809910260800?thread_ts=1542809318.260400&cid=C03MSG8B7

Relevant logs and/or screenshots

Output of checks

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)

Edited May 19, 2022 by Coung Ngo
Assignee Loading
Time tracking Loading