Actions
Patch #18440
closedJournals could be ordered using the create_on attribute instead of the id
Status:
Closed
Priority:
Low
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Description
It is usually equivalent to sort Journals by id or to order them using the create_on attribute.
However, when importing values from an external source to the Journals table, we sometimes cannot rely on the id to give a correct order.
So here is a very tiny patch to fix that.
Thanks!
Files
Related issues
Updated by Go MAEDA about 10 years ago
- Related to Defect #14881: Issue journals should be ordered by created_on, not id added
Updated by Go MAEDA about 10 years ago
- Status changed from New to Closed
Thanks for submitting the patch but this issue duplicates with #14881.
Updated by Go MAEDA about 10 years ago
- Related to deleted (Defect #14881: Issue journals should be ordered by created_on, not id)
Updated by Go MAEDA about 10 years ago
- Is duplicate of Defect #14881: Issue journals should be ordered by created_on, not id added
Actions