General
-
Process Editor with parent/child steps to frustrating.
When I have a few Parent processes with some Child process in them, The Process Editor is very hard to use. You get that dreaded "Menu Options unavailable while viewing a parent or its child steps." Comment box appear. The problem is that there is no other way to do Parent tasks like add a child step now that you have a "parent or its child steps" selected. Only when you click into another Parent step can you access the Parent process menu. This is hugely frustrating when you are working of creating a bunch of child steps.
Please change…
1 vote -
Support for High Priority Deployments/Tasks
Sometimes our task queue is filled with a lot of tasks waiting to be executed. Every once in a while a priority deployment needs to take place at the same time.
In such case It would be very useful if we could mark this deployment as "High Priority", so that the tasks of this deployment are handled before the already existing tasks in the queue.
This is not possible now, the only solution now is to cancel all the existing tasks.101 votes -
Add support for SVN (subversion) VCS commit information
After pushing build information from a TeamCity project that was building some code from SVN (subversion) version control system, I noticed that while the package in octopus did have the commit section filled out as expected, the commits were NOT there when creating a release with that package. This meant that we couldn't automatically generate the release notes based on commit messages. I contacted octopus support and we eventually figured out that SVN is not supported.
4 votes -
Support the creation of custom permissions
Octopus has the ability to create custom roles, but not to introduce new permissions. We would like to be able to add new custom permissions and then have both a REST api and script access that lets us test if a role has that permission. This would let us extend the Teams / Users / User Roles model to cover finer grained decisions more gracefully than a proliferation of user roles.
1 vote -
Better integration between runbooks and deployments
When deploying to c:\mydirectory#{Octopus.Release.Number} Runbooks are unable to obtain the #{Octopus.Release.Number} information from the deployment. Which makes a lot of actions rather difficult.
If it was possible for a deployment to set a variable available to Runbooks or for Runbooks to query information in releases per environment that would really be great.2 votes -
Streamline data entry. SN, and other data must be entered multiple times for one transaction
Streamline data entry
1 vote -
Support inserting into an array in JSON Configuration
Given an JSON settings file which has an array element
e.g. { "Users": [] }
Use Octopus variables to insert into the array rather than just replace values.
e.g.
define Users:0:Username = user
define Users:0:Password = passwordWould result in the object getting inserted
{ "Users": [ { "Username: "user", "Password": "password" } ] }
https://help.octopus.com/t/json-configuration-can-it-insert-into-an-array/24317/7
14 votes -
Tenant variables side by side
The idea is to have the tenant variables displayed vertically, with one column for each environment.
Currently, it is quite tedious to compare or copy variable values from an environment to another.13 votes -
See references to projects used in 'Deploy a Release' steps
In a given project, see all the other projects that refer to it in a 'Deploy a Release' step.
Use case for this is similar to the Usage tab for a step template. If I create a new release for a sub-project, I want to be able to find each parent project and update them to point to this new release.
9 votes -
Datetime filter for Octopus APIs
Octopus does not provide date time filter for any of the Octopus APIs.
Which makes very difficult to pull data for an older date.
There is no way other than loading each page then take the Page.Next value and compare the date.
Its time consuming when the date we search is really old.I would like Octopus deploy to support the date filter for APIs.
There is one more drawback while using APIs with out date time filter which is explained in this page.
https://help.octopus.com/t/date-filter-for-octopus-apis/25111/31 vote -
Right-click "Open link in new tab" no longer working
This was previously asked for and done here https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/3133236-non-javascript-based-links
But we updated from 2019.6.8 to 2019.9.10 and this has broken in at least one spot.
If you click "Project switcher" and search for a Project the dropdown no longer gives links that can be open in a new tab.
This makes me sad. :(
11 votes -
Deployment promotion with excluded steps is not persisting chosen steps
Currently if we create a release for a project with multiple steps excluding some of the steps, it is not persisting the state when the same release is promoted to the next environment as part of channel life cycle.
We need to exclude the steps again when promoting the same release to next environment which is causing lot of problems as people deploying the release are different for different environments and often they forget.
It would be great if you can persist the state of excluded steps to the next environments as part of same release?
15 votes -
Deploy a release - accessing variables from last release
As per - https://help.octopus.com/t/deploy-a-release-accessing-variables-from-last-release/22788
You should be able to access a previous releases Step output variables, for when a release has already been deployed.
Either via the Deploy a release step.
Or more generally to retrieve these values for a given release.
E.g. an obtain Release information step3 votes -
"Deploy a release step" allow choosing target environment
The deploy release step assumes want to deploy to the same environment as the parent deployment.
Add facility to pass a parameter to chose which environment to deploy the release too.
E.g. so can deploy a single master release, which kicks off multiple deployments of other release to the defined environments specified by the parameters.Similar to how the community Chain step template allows for.
3 votes -
Improve filtering on the Overview page
I would love it if there were more options for filtering on the Overview page.
I use this page as the main page I visit when searching for a release to deploy (e.g. to my dev or test environment). Since we have releases for every commit on every branch, it can be a bit of work to find the release I am looking for sometimes.
What I suggest is:
- A filter for channels (e.g. I want to only show 1 channel)
- A filter for the version number/release name. This should essentially be a search box where I can…1 vote -
Allow downloading and restoring configuration from audit history
Currently the audit API can only return an HTML annotated view of the changes made to configuration elements like variable sets and deployment process. This is not helpful when the configuration is huge or when we need to find changes over multiple edits of the same configuration.
Proposal: add the ability to download the raw JSON that was in effect after the change. The result should be equivalent to what we would get by clicking 'Download as JSON' after making the changes.
This would allow us to:
- create diffs between arbitrary dates, not just a single entry in the…3 votes -
Allow the visibility of what teams have access to a project/group
Right now you can view a Team and see what project or project group that team has access to. We'd like to see the reverse as well. When we go to a project or project group we'd like to see the teams that have access along with their permissions.
10 votes -
In the deployement process edit, edited step is not scrolled up
When i edit a step in deployment process I see left side pane steps starting from 1,2.....etc. i don't see the one I am editing scrolled up.
1 vote -
Pre-caching / Pre-acquiring of packages for scheduled deployments
We deploy our packages to our customer environments.
For example 1.5GB of packages to 500 targets over the internet. As the internet connections can be slow and to make sure that the deployments all take place at the same (scheduled) time I suggest that the "acquiring packages" step optionally starts as soon as a deployment is scheduled and verified again at the scheduled execution time. Should the deployment package(s) be missing or corrupt at the scheduled execution time there could also be an option "re-aquire at execution"/"fail if missing".3 votes -
Consider turning Octopus into a complete CI\CD Solution
all-in-one tool combining source control (or VCS integration), artifact storage, package feeds, build & deploy pipelines.
I love Octopus and have used it for years now. The flexibility you offer with your product in the deployment arena is awesome. Simple things I take for granted are not offered or a pain in other solutions such as Azure Devops.
1 vote
- Don't see your idea?