Originally asked by SDGTLS on 08 December 2020 (original question)
We want to sync a Task from instance 1 to instance 2 and then make this task to a subtask of another ticket in instance 2. And from now on no more syncing is possible.
Comments:
Serhiy Onyshchenko commented on 09 December 2020
Hello, SDGTLS.
Quick question: what should be the parent task of the sub-task on instance 2?
I mean is it always the same parent task, or is it somehow inferred from the task of instance 1?
Or maybe you wish to configure Exalate such that once the issue is synced from instance 1 to instance 2 it’s synced as a parent task, but then some user has to manually convert it into a sub-task?
SDGTLS commented on 09 December 2020
The parent task will be a separate Task in instance 2. We use that parent task as a container to group tickets for example for a support retainer.
SDGTLS commented on 09 December 2020
Just a very quick drawing of what we need
Serhiy Onyshchenko commented on 09 December 2020
Thanks for the explanation and the drawing SDGTLS , just to clarify: is it a requirement that Exalate syncs the issue from instance 1 to instance 2 as a Task so that a user manually converts the task on instance 2 to sub-task, or would it be fine, if Exalate creates the issue on instance 2 as a sub-task on step 1?
SDGTLS commented on 09 December 2020
“is it a requirement that Exalate syncs the issue from instance 1 to instance 2 as a Task so that a user manually converts the task on instance 2 to sub-task” yes it is
“is it a requirement that Exalate syncs the issue from instance 1 to instance 2 as a Task so that a user manually converts the task on instance 2 to sub-task” sadly not because at this point we sometimes don’t know if there is a Parenttask
Serhiy Onyshchenko commented on 09 December 2020
OK, got it, thanks!