[MGNLMIGRATION-155] Handle the sub-task calls from the main migration task Created: 29/Oct/12  Updated: 29/Nov/12  Resolved: 08/Nov/12

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

Type: Improvement Priority: Minor
Reporter: Jozef Chocholacek Assignee: Jozef Chocholacek
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
is depended upon by MGNLMIGRATION-156 Add a "recordSubtaskCall" method Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When there is a main task that calls sub-tasks and reports such calls, then every enter and return creates new JCR node for the main task (because the change of the current task). We can live with that, but it's not the ideal solution. It'd be better if the main task has just one JCR node with all the records.


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