Project

General

Profile

Actions
Copy link

Defect #14674

closed

IssuePriority expects database counters to be pristine

Added by Daniel Sundström almost 11 years ago. Updated almost 2 years ago.

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

0%

Estimated time:
Resolution:
Wont fix
Affected version:
2.3.2

Description

IssuePriority expects implicitly that the autoincrement counter on the Enumerations-table begins at 0, something
which might not be case when migrating a Redmine installation from one machine to another one.

The result is that all issues are marked graphically as high-priority issues if the counter is off by one or two - or not marked at
all of the counter is off by more than that.

The attached patch changes the IssuePriority to rely on internal position rather than id for selecting proper CSS-classes which
resolves the issue.

Files

redmin-git-patch.diff (724 Bytes) redmin-git-patch.diff Daniel Sundström, 2013-08-12 20:43

Related issues

Related to Redmine - Feature #12216: Textual CSS class for prioritiesClosedJean-Philippe Lang

Actions
Actions
Copy link

Also available in: Atom PDF