More info on Zendesk Ticket#202459
Our team needs an API that allows us to confidently copy a task into a release from an outside template. This is crucial for our workflow
by: Spencer M. | 3 months ago | Templates & Releases
Planned
5
Need copyTask API in XL Release to allow the copying of tasks from one template/release to another
by: Spencer M. | 3 months ago | Templates & Releases
Copyright © 2023, Digital.ai Software, Inc. All Rights Reserved
Comments
Thank you for the suggestion.
When copying tasks, do you typically copy them within the same folder releases, or do you copy them to releases on different folders?
If it's the latter, how do you anticipate the behavior of assigned teams and variable functionality in the new folder? Would the copied task carry those dependent values, would leave them empty, or some other behavior?
Releases are typically started in a "team" folder. Then we copy in tasks from a template in a different "helper" folder.
When a task gets copied, I would expect it to get copied as is. Meaning assignees, variables, inputs, locked status etc. all would get copied into the new release exactly. The whole point of this functionality is to have one copy of this task that can be copied into a release started from any template. I would also expect that when the task gets copied, the original "source" task does not change at all. That way it can be copied over and over without getting messed up.
It is really necessary
We'll be dedicating our efforts to exploring potential solutions within the 24.3 (Fuji) timeframe. We'll then share our findings with the Digital.ai Community and may also conduct additional discovery interviews for further insights on the proposal.