[MGNLMIGRATION-145] Add a timestamp to module and script nodes Created: 23/Oct/12  Updated: 03/Dec/12  Resolved: 03/Dec/12

Status: Closed
Project: Migration 4.4 to 4.5 (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2

Type: Improvement Priority: Neutral
Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLMIGRATION-175 Fix DefaultReportingServiceTest due t... Sub-task Closed Jozef Chocholacek  
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Store last task/script ID to be able to continue the series after the system restart (i.e. when inmemory counters are reset).

I've decided to add a timestamp to the name of a module or script node. That will enable "adding" to the report (i.e. on multiple migration run), and also make the report more clear.



 Comments   
Comment by Jan Haderka [ 02/Dec/12 ]

No commit associated w/ this issue.

Comment by Jozef Chocholacek [ 03/Dec/12 ]

Sorry, forgot to push. Anyway, there are failed tests now, I have to fix these before I re-resolve this issue.

Comment by Jozef Chocholacek [ 03/Dec/12 ]

Tests adjusted, changes pushed.

Generated at Mon Feb 12 10:17:35 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.