Show due date in gray when issue is closed in issues list
What does this MR do?
This MR updates the issues list to show due dates in gray for closed issues. When an issue is closed, there is no longer an urgency to complete it so the due date does not need to be in red.
The issues list is current in Haml, but there is also a Vue refactor behind the feature flag vue_issues_list so this MR updates both places
Issue: #9202 (closed)
Screenshots or Screencasts (strongly suggested)
| before | after |
|---|---|
 |
 |
How to setup and validate locally (strongly suggested)
- (Optional) In rails console enable the
vue_issues_listfeature flagFeature.enable(:vue_issues_list) - Visit an issue and set its due date to the past and then close it
- Visit any group or project issues list and confirm the due date on the closed issue is not red
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Coung Ngo