Settings and activity
8 results found
-
11 votes
An error occurred while saving the comment -
9 votes
An error occurred while saving the comment 
Patrick
commented
I see this only has a small number of Votes but could this be included? It's a "Low Hanging Fruit" which would be very helpful.
Quite often we find variables are updated for the wrong environment. We have 5 or 6 environments, each with 40 or 50 variables. I assume people are getting lost in the massively long list of variables and accidentally updating the variable for the incorrect environment.
The ability to expand agroup for the relevant environment should be a fairly easy task technically and would help reduce the chance for human error.
-
17 votesPatrick
shared this idea
·
-
1 votePatrick
shared this idea
·
-
64 votes
An error occurred while saving the comment Patrick
commented
This is must have functionality which I would have thought would be relatively easy to include and help so many people!
Patrick
supported this idea
·
-
57 votesPatrick
supported this idea
·
An error occurred while saving the comment Patrick
commented
I agree this is a good idea. If I update status.io at the end of my deployment with a deploy success\fail and the call to status.io fails, the deployment is considered to be a failure. However, failing to update the status.io page at the end shouldn't mark the whole deployment as a failure.
-
119 votes
An error occurred while saving the comment Patrick
commented
I'm surprised this feature isn't already available. Creating a parent website is a fundamental requirement for many IIS projects.
Patrick
supported this idea
·
-
1 vote
An error occurred while saving the comment Patrick
commented
Patrick
shared this idea
·
There seems to be a number of UserVoice topics related to this same issue which makes the voting process difficult. I think if someone accumulated the votes across all the related topics this issue would have a much higher ranking.
One other related topic is
https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/15957697-make-variables-groupable-collapsable
This seems to be a "Low Hanging Fruit" which would be very helpful.
Quite often we find variables are updated for the wrong environment. We have 5 or 6 environments, each with 40 or 50 variables. I assume people are getting lost in the massively long list of variables and accidentally updating the variable for the incorrect environment.
The ability to expand agroup for the relevant environment should be a fairly easy task technically and would help reduce the chance for human error.