Dont show due date in red on epic related issues
What does this MR do?
Similar to the problem in #9202 (closed) issues shown in the epic related items tree have a due shown in red even when the issue is closed. This is because the closed state is not provided to the item-due-date component.
Screenshots or Screencasts (strongly suggested)
Before the fix, due dates of closed issues would appear in red colour, indicating the due date was missed.
After the fix, due dates of closed issues appear in normal font color.
How to setup and validate locally (strongly suggested)
- create an epic
- create an issue
- set a due date in the past
- link it to the epic
- create a second issue
- set a due date in the past
- link it to the epic
- close this issue
- view the epic and its list of related issues - the due date is now correctly displayed
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 Daniel Ziegenberg