Project

General

Profile

Actions

Feature #31881

closed

Add "behind-schedule" CSS class to issues

Added by Go MAEDA over 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Issues
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

"behind-schedule" class, which is already available in gantt, indicates that the issue is behind the schedule. This means that the done ratio is lower than expected.

In gantt, "behind-schedule" issues are shown in orange color. I think also issues list and issue detail page should have "behind-schedule" class in order to be able to implement the same coloring as gantt.

It is beneficial for project management to warn before the deadline is over.


Files

31881.patch (2.29 KB) 31881.patch Go MAEDA, 2019-08-19 16:41
31881-v2.patch (1.09 KB) 31881-v2.patch Go MAEDA, 2020-07-05 05:44

Related issues

Related to Redmine - Feature #7455: Search for issues that are behind scheduleNew2011-01-26

Actions
Actions #1

Updated by Go MAEDA over 4 years ago

Here is a patch.

Actions #2

Updated by Go MAEDA over 4 years ago

  • Target version set to Candidate for next major release
Actions #3

Updated by Go MAEDA almost 4 years ago

  • Related to Feature #7455: Search for issues that are behind schedule added
Actions #4

Updated by Go MAEDA almost 4 years ago

Updated the patch.

Changing the appearance is controversial, so I would like to just add a CSS class. UI changes should be discussed in a new issue.

Actions #5

Updated by Bernhard Rohloff almost 4 years ago

+1 It's a nice improvement and makes the modules more consistent.
Also a good indicator if an issue needs a bit of attention.

Actions #6

Updated by Go MAEDA almost 4 years ago

  • Target version changed from Candidate for next major release to 4.2.0

Bernhard Rohloff wrote:

+1 It's a nice improvement and makes the modules more consistent.

Thank you for checking the patch. Setting the target version to 4.2.0.

Also a good indicator if an issue needs a bit of attention.

I will open a new issue to discuss UI that indicates the issue is behind schedule.

Actions #7

Updated by Go MAEDA almost 4 years ago

  • Status changed from New to Closed
  • Assignee set to Go MAEDA
  • Resolution set to Fixed

Committed the patch.

Actions #8

Updated by Toshi MARUYAMA almost 4 years ago

  • Status changed from Closed to Reopened

Tests fails.

Failure:
Redmine::WikiFormatting::MacrosTest#test_issue_macro_should_render_link_to_issue [/REDMINE/WORK-DIR-NO-RAID/hg-workdir/my-work/test/unit/lib/redmine/wiki_formatting/macros_test.rb:414]:
--- expected
+++ actual
@@ -1 +1 @@
-"<p><a class=\"issue tracker-1 status-1 priority-4 priority-lowest\" href=\"/issues/1\">Bug #1</a>: Cannot print recipes</p>" 
+"<p><a class=\"issue tracker-1 status-1 priority-4 priority-lowest behind-schedule\" href=\"/issues/1\">Bug #1</a>: Cannot print recipes</p>" 

bin/rails test test/unit/lib/redmine/wiki_formatting/macros_test.rb:412

Actions #9

Updated by Go MAEDA almost 4 years ago

  • Status changed from Reopened to Closed

Tests fails.

Fixed in r19869.

Actions

Also available in: Atom PDF