Feature #27316

Highlight due date of overdue issues in the issues list

Added by Jorge Garcia over 2 years ago. Updated almost 2 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Go MAEDA% Done:

0%

Category:Issues list
Target version:4.0.0
Resolution:

Description

I do not know if it will be a defect but in the issues view, the expiration dates are not marked in red. Only marked when i opend the issue

Sin título.jpg (259 KB) Jorge Garcia, 2017-10-27 22:25

27316-highlight-overdue-issue.diff Magnifier (597 Bytes) Go MAEDA, 2017-10-28 09:07

highlight-overdue-date@2x.png (54.7 KB) Go MAEDA, 2017-10-28 09:07

Related issues

Related to Redmine - Feature #20812: Highlight overdue issues and private issues in issue list New

Associated revisions

Revision 17483
Added by Go MAEDA almost 2 years ago

Highlight due date of overdue issues in the issues list (#27316).

Patch by Go MAEDA.

History

#1 Updated by Go MAEDA over 2 years ago

  • Related to Feature #20812: Highlight overdue issues and private issues in issue list added

#2 Updated by Go MAEDA over 2 years ago

  • Tracker changed from Defect to Feature
  • Subject changed from Do not mark in red the end dates expired in the issues view to Highlight due date of overdue issues in the issues list
  • Category changed from Issues to Issues list

#3 Updated by Go MAEDA over 2 years ago

I think the request is reasonable. Highlighting due date of overdue issues in the issues list as well as an individual issue page will improve usability and consistency.

I wrote a patch to implement this request.

#4 Updated by Go MAEDA over 2 years ago

  • Target version set to 4.1.0

#5 Updated by Jorge Garcia over 2 years ago

  • Status changed from New to Resolved

#6 Updated by Bernhard Rohloff over 2 years ago

@Go MAEDA
I'm just curious...
Is there a reason/strategy behind assigning this one line change to 4.1.0 instead of an earlier release?

#7 Updated by Go MAEDA over 2 years ago

  • Status changed from Resolved to New

Bernhard Rohloff wrote:

Is there a reason/strategy behind assigning this one line change to 4.1.0 instead of an earlier release?

Jean-Philippe Lang wants to release Redmine 4.0.0 as soon as possible. Therefore, I don't add open issues for Redmine 4.0.0.

#8 Updated by Bernhard Rohloff over 2 years ago

Ok, this totally makes sense. Thank you for your explanation.

#9 Updated by Go MAEDA almost 2 years ago

  • Status changed from New to Closed
  • Target version changed from 4.1.0 to 4.0.0

Committed.

#10 Updated by Go MAEDA almost 2 years ago

  • Assignee set to Go MAEDA

Also available in: Atom PDF