This was originally raised at https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6186352-version-control-of-deployment-scripts and closed as completed with a solution of scripting the import/export tool.

Raising as a new suggestion as this has come up as few times in support calls and some people have suggested on the original thread that the import/export tool doesn't meet their needs. (Didn't want to reopen the original thread as some people are happy with the provided solution in that thread.)

"In the Continuous Delivery book, Jez wrote that your deployment scripts should be in source control. After creating some pretty elaborate powershell scripts for Octopus, I have to agree. Losing those scripts or having them damaged would be pretty painful.
I understand Octopus has backups, but it would be better to be able to get back to a previous version or see where the script had changed. Since we use GIT, I would be completely satisfied if GIT integration was all that you supported. :) I hope this is helpful. Thanks."

The variables view is very basic and it generally needs improving since it quickly gets hard to use when you begin adding lots of variables.

1. You have to add the same variable name for multiple environments and the ordering of environments is not the same. This is error prone and makes the list hard to parse.
2. There is no description for variables so you need to add very long names sometimes. This has already been covered, but I added it for completeness. See https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6079578-enhance-the-variable-maintenance-screen-with-varia
3. There can be different types of variables which are changed for different reasons. It would be great to have a category concept to group them with.
4. For very large numbers of variables it would be great with a search box which filters the variables as you type. It should also search in the description.

See the following mockup for an example:
http://s288.photobucket.com/user/withoutprecedence/media/OD%20variables%20view_zpsfesl13ke.png.html

Octopus is a deployment orchestration/application release automation tool. Many companies can benefit from configuration management tools like Puppet/Chef, but for various reasons are unable to use them. On the Windows platform, PowerShell's Desired State Configuration support is designed as an alternative to Puppet/Chef, and makes it easy to automate tasks like configuring Windows features and checking for drift.

However there are limits to using PowerShell DSC for our customers - they may not always be on the same AD domain, there may be security issues, there's no auditing, and no nice central way to manage scripts for the team.

Octopus could build in support for DSC, and this would make it much easier for customers to create DSC configurations and apply them to machines managed by Octopus.

The ability to import step templates from other locations (e.g. Octopus Library) is awesome, but if someone updates the step template the import process can not be used to update the copy I have in my Octopus server. I'm forced to delete the step template and re-import it. Obviously if I have N projects that rely on the step template I'm now stuck because I can't delete it when projects are using it.

Since I can technically update the powershell script and change parameters and so on inside of Octopus Deploy UI itself, importing of existing step templates should just offer to do the same thing and update the pieces for me.