You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to clone pipelines/workflows from one environment to another.
While cloning it created the workflow with suffix as "-clone-#hash" which I do not want.
Since I am copying a lot of applications so editing workflows name one-by-one will be a very time consuming task.
So can we please add an option to give custom workflow name while cloning.
🎤 Pitch / Usecases
I want to clone pipelines/workflows from one environment to another.
While cloning it created the workflow with suffix as "-clone-#hash" which I do not want.
Since I am copying a lot of applications so editing workflows name one-by-one will be a very time consuming task.
So can we please add an option to give custom workflow name while cloning.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🔖 Feature description
I want to clone pipelines/workflows from one environment to another.
While cloning it created the workflow with suffix as "-clone-#hash" which I do not want.
Since I am copying a lot of applications so editing workflows name one-by-one will be a very time consuming task.
So can we please add an option to give custom workflow name while cloning.
🎤 Pitch / Usecases
I want to clone pipelines/workflows from one environment to another.
While cloning it created the workflow with suffix as "-clone-#hash" which I do not want.
Since I am copying a lot of applications so editing workflows name one-by-one will be a very time consuming task.
So can we please add an option to give custom workflow name while cloning.
🔄️ Alternative
No response
👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: