In some situations it would be extremely time-saving to have a button in a release that allows you to reload changes from a template. This would only affect the open Tasks.
If the original template is deleted, you could select a template to reload from.
Just for completeness, I don't care if it's a button. It can be some kind of API or a page where I can choose the releases to reload and the template.
Best regards
Markus
by: Markus M. | 6 months ago | Templates & Releases
Comments
Could you kindly provide more details about this idea? What is the exact use case, and how do you envision the task of "mapping" between the current release and a given template being carried out?
An example would be a bug in a Groovy script. Now I have to fix it in the template and in every release that is already running manually. With this functionality, I would save a lot of time by just fixing it in the template and letting the automation do the rest.
The "mapping" depends heavily on the method you choose to implement this functionality. Is it an API, a button in the release or something else
Thank you for the update. We will have a broader discussion with the engineering team and follow up on this thread in June.
We are currently developing a copy task functionality that will allow users to reliably copy tasks, including group tasks, among releases, templates, and workflows.
We hope this functionality will provide a good alternative to meet this need. We will invite customers to provide feedback on the proposal for the copy task behavior as well. You can track progress on this idea here: https://ideas.digital.ai/devops/Idea/Detail/4146 .
Our goal is to deliver an API solution in the 24.3 release, followed by a UI solution later on.