Edit ordering of Library variable sets.
We should have an option to reorder the library variable sets. This will be very helpful when a large number of Library variable sets are used and need to be organised.
Jon Clausen commented
Paul Farry commented
In the work that we are doing with Octopus, we have a number of "Core" aka Base Library sets that developers can choose from and 95% of the time these will be correct, except when a particular project may need to override those values in a specific (libraryset) for that work (and there might be a few deployable projects involved in the development project).
The original base project may provide all the logging database etc, but for this project we need to override the connectionstring for example. The ordering makes this unpredictable as to what the variables will become unless you override it in every projects private variables.
Having the ability to explicitly set the order would make this work much simplier.
Peter Hageus commented
Yes, wan't this badly, would improve the experience of setting up a new tenant a lot.
Róbert Varga commented
This feature would be awesome, I hate the order of my variables but I make them as I need them.
Seiji Suenaga commented
I've wanted this repeatedly over the past several months.
Dan Anstis commented
We definitely need this, as our project variables expand over time the only way we can keep like variables together is to remove them all and recreate.
Paul Reynolds commented
Yes please, it would be much more user friendly to be able to populate related variables together, and help to avoid mistakes
We could really use this...
Yes, I'm encountering the same issue and am wasting my time recreating all the variables again, hoping that I don't make a typo.
Luke Saunders commented
It would be very useful to be able to change the order variable templates. If there is a change, we currently have to delete all, and re-enter them in the required order.
Jon Kennerly commented
My first at setting up tenant deployment of "clients", and the first thing I notice is that the template order is not adjustable. The only options is that you have to start over and make sure you put them in the order you need the first time.
In our case:
A client has a full address (address1, address2, zip, state). There are other attributes.
At some point we might add in a Phone number attribute. It would make sense in a visual form flow for the phone number to be near the Address fields. This is good for the dev-ops guys or whoever is inputting in such values.