Allow cloning Library Variable Sets
Allow cloning of library variable sets so it becomes easier to create a new variable set for a new environment.

-
Daniel Spindler commented
Would this really take long to implement? Cannot see how it would take long. Just get it done.
-
Bill Fahle commented
Sign me up for yes. It's painful to bring variables across deployments or when adding new tenants.
-
Neil commented
really need this
-
Anonymous commented
Something that should be implemented years ago...
-
anonym commented
please implement it, since this demand is around for years +1
-
J Foster commented
+3 - This would make life so much easier.
-
Mark Regan commented
I really cannot understand why this is not a thing. Just about to embark on the maddening task of find a workaround for this oversight. So I'm a yes :)
-
Anonymous commented
YES PLEASE
-
Anonymous commented
Definitely voting for Variable set clone in the UI!! Thank you, it would be awesome!!!
-
Tom commented
Why is this not an obvious and easy thing to implement and why is this still a problem in 2018?
-
Anonymous commented
There is Google Chrome extension available and we are also using.
https://chrome.google.com/webstore/detail/octopus-variable-copier/bcdafjjfijobmknkbfjbkiagajgiibga -
Anonymous commented
+1
-
Anonymous commented
+1
-
Anonymous commented
This is probably the most annoying "worst feature" in Octopus. The ability to clone variable sets would make life so much easier.
-
Anonymous commented
This Would save me a massive amount of time. I'm so sick of having to have Octopus open in two windows to copy a set of variables for new environment. I was really disappointed not to see this in v4.
-
Anthony Geoghegan commented
Rather than for new environments, I consider this a potentially easy way to apply temporary alternative environment settings that allow for rapid switching back and forth. It might be great for disaster recovery say.
-
Anonymous commented
Voting!