-
Allow worker pools to be compatible with ALL process steps
Worker pools only are compatible with two OOTB Octopus process steps (deploy a script, deploy to cloud). My team heavily uses the 'Deploy a Package' step, but this step is not allowed to use worker pools. This is quite an oversight and should be a prioritized feature in the next sprint.
1 vote -
Allow middle mouse button click or ctrl + click to select items in search dropdown.
In some previous version of Octopus, I was able to do this. I always used the search dropdown to open up multiple projects at a time using middle mouse button click.
1 vote -
Project Group as collapsible panel (like Expand/Collapse)
Can we add collapsible panel (like Expand/Collapse) to Project Group. Most of the time I have to scroll down to search my projects, so it would be easy if we add expand collapse section.
1 vote -
Execute F# script steps using dotnet fsi
Several packages are now incompatible with FSI as it uses the old execution engine, one example is FSharp.Data and latest Newtonsoft.Json. System.Text.Json is also out of the question, basically anything targeting Netstandard 2.0.
Switching to
dotnet fsi
will allow usage of said packages. It will also ensure cross platform compatibility for scripts and allows referencing packages in the script. https://devblogs.microsoft.com/dotnet/f-5-and-f-tools-update-for-june/5 votes -
Permanent fix for Octopus-Jira integration to evaluate release notes for dynamic pckages
Permanent fix for Octopus-Jira integration to evaluate release notes for dynamic pckages.
This is critical for end to end visibility in Jira.
2 votes -
Allow a "not" mode for filters
We have a dev cluster set up and working with octopus.
One of the hurdles to creating ephemeral/adhoc debug/testing environments at the moment is the fact that we have to go in and manually map those environments in lots of different places.
Ideally, we'd be able to create a resource (e.g. a kubernetes cluster, certificate, etc), that lets us specify that it is a valid resource for ALL environments EXCEPT production.
1 vote -
Deploy a Release Step - Task Summary View
We have a "master" deployment project that runs a bunch of "Deploy a Release" steps that run other projects. We would love to be able to monitor each of the sub projects from the master. Right now to view the details of a "Deploy a Release" step you see something like this: Deploying release 2020.5.0-beta.14 of project 'ZYX'. View deployment.
When you click View Deployment you are taken to another page to monitor the progress. We would love to see all that information displayed on the master project so we don't have to drill down.
1 vote -
Add dates range in Octopus task filters
if we can have date filter in the task section then it will be ease to get the data for a particular time period.
TASK ---->Advanced Filter
3 votes -
JSON Template for Subscriptions
Allow the json payload used when setting up Subscriptions to be templated in the same way as config.
If you could specify the json with embedded octopus variables you could integrate with many many other tools without the need to add a custom step at the end of each deployment. (eg. MS teams)2 votes -
Expose Octopus.Deployment.Targets during deployment
The current Octopus.Deployment.Targets variable is only available to the Deployment Changes section. It would be beneficial to expose this information during the deployment too.
The use case in mind is sending emails pre-release that mention the machines that will be deployed to, or in the case of Azure, could expose the URLs, given these work on the convention of <machine-name>.azurewebsites.net2 votes -
Allow variable in variable set to have a Project Group scope
It would be useful if we could set variables in a variable set to a Project Group scope.
The use case for this is that we have a shared variable set that sets a product ID.
We could then scope this by product group.
eg
Variable Set Products
Product Id - ATeam Scoped to Project Group A
Product Id - BTeam Scoped to Project Group BProject Group A
- Proj A1
- Proj A2Project Group B
- Proj B1
- Proj B2Currently we have to override the ProductID in every project in Project Group B which sometimes…
2 votes -
Add more regional support to Octopus Cloud
Octopus Cloud is presently limited to three Azure regions (West US 2, West Europe, Australia East).
Strict data sovereignty rules for some customers may mean that Octopus Cloud is currently not a viable solution.It would be good if more regions were supported by Octopus Cloud - specifically UK West and/or UK South.
Also - how does Octopus handle high availability and fault tolerance if limited to only one region?
2 votes -
prompted variable calculated default value
Allow the default values for prompted variables to be calculated, instead of a constant.
4 votes -
Add date, time and date/time variable types
Add date, time and date/time variable types. This would validate that the input value is a valid date, time or date/time.
Optionally provide a friendly interface (date picker control) for the respective values.
4 votes -
Tenant "overview" page is not intuitive
I find that the most common task performed on tenants is modification of tenant variables. However, I feel that the UI does not support this task very well.
I find that once I click through on the tenant, my next step is to click on the project in which I wish to set variables for which does not result in the expected action (it takes you to the project instead).
My recommendation is that the tenant variables becomes the landing page for tenants and the project administration for the tenant could become a secondary page (or perhaps it could even…
1 vote -
Allow a runbook to be able to be run from another runbook
With standard octopus deployment there is a "deploy a release" step which can be used to run other projects from a parent project.
It would be usefult o have a similar "run a runbook" step to be able to build up run books from smaller steps into bigger processes.
Our use case is swithcing to DR, there are numerous steps such as stopping various services, starting other services, stopping replication etc. But, each of these steps is also useful in itself so we have steps effectively duplicated, once in the invoke dr runbook and once in a runbook all by…
4 votes -
codebuild
Add an official Octopus plugin for AWS CodeBuild to integrate with Jira.
https://octopus.com/docs/managing-releases/issue-tracking/jira#availability
5 votes -
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 -
Ability to set application URLs for each environment, allowing linking from dashboard
It would be great if the Octopus dashboard, which displays the current releases of each application in each environment, contained links to the applications in the specific environments. E.g. if the box displaying details of the most recent deployment of Application X to Environment Y also contained a link to that app in that environment
We presently maintain this info outside of Octopus, in Wiki pages etc, but it’s a pain to maintain.
It would be great if this was directly available in Octopus, because the matrix of applications to environments is already there. Forcing users to access the links…5 votes -
'dotnet octo pack' multiple packages in one command (Octopus.DotNet.Cli)
The OctoPack project is great for Framework projects. We add the nuget dependency to select projects and add
/p:RunOctoPack=true
to our build script. The build script does not need to be updated for every new, removed or renamed octo-packed project.SDK projects are less automated. After building, we have to run
dotnet publish
, thenocto pack
for each project. It would be great to define 1 build script, then update the projects as needed to pack or not.Idea to attain goal:
Add element
<IsOctoPackable>true</IsOctoPackable>
in csproj that works similar to IsPackable.Allow
dot net octo pack
to point…
5 votes
- Don't see your idea?