Project

General

Profile

Actions
Copy link

Defect #4657

open

Wrong timestamp for import of entries of the last ChangeSet.

Added by Karl Heinz Marbaise about 14 years ago. Updated about 13 years ago.

Status:
New
Priority:
Normal
Assignee:
Toshi MARUYAMA
Category:
SCM
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:
0.8.7

Description

If you decided to remove the configured SCM System and delete the entries (Settings - Repository) and press the delete button after that all entries in the database for SCM changes are removed.
If you like to redo this you have to go via Settings - Repository and configure the SCM system (in my case SVN) and reread the entries from the SCM system.
The problem is that an entry (changeset) which closes an item (via 

 fixed #xxx
) will be put into the database with the wrong timestamp...based on my experience it is the current timestamp instead of the timestamp of the changeset has been done (in SVN).
But this seemed to be only happen for the last changeset which is done via the first time import.

Files

Download all files
screen-error.png (54.9 KB) screen-error.png Karl Heinz Marbaise, 2010-01-26 12:52
Terminal_—_less_—_66×23.jpg (96.4 KB) Terminal_—_less_—_66×23.jpg Josh Sharpe, 2010-04-15 03:34

Related issues

Related to Redmine - Defect #5357: Git: SCM revisions ordered by date/time (should be reverse commit order)NewToshi MARUYAMA2010-04-20

Actions
Actions
Copy link

Also available in: Atom PDF