315 results found
-
Navigation and updates
For enterprise users with a dozen teams sharing an instance of Octopus, navigating and making updates is pretty cumbersome. So for instance, we have over 20 life cycles, so if I make a change and save, I get sent back to the top of the list so that I then have to scroll back down to the life cycles I'm interested in. Environments is even worse, with over 70, but only 6 I care about. Some filtering on the pages or just a top level line of business/division filter would be great.
1 vote -
Less clicking, more doing
There is way too much clicking and scrolling that needs to be done in order to manage/administrate/setup a deployment process.
Some examples:
Change the name of a deployment project, but don't save yet. Click the button to upload a new logo for the project. You get a warning about discarding changes. Why? I'm not done changing my project settings.
There's a little "hamburger" menu on the left side of each deployment project process step. But it's useless. For example, why not have options in the menu to "Run in parallel with previous step" or "Run after previous step" (the opposite…
2 votes -
Separate lifecycle phases
I find it confusing when we have all the stage environments and production environments inline.
I'd love to see the phases separated into different rows.
Example: I have two phases, Production and Stage.
https://i.imgur.com/1zU4KG0.png1 vote -
Make variables groupable/collapsable
In the project I'm currently working in; we have 6+ environments and many variables are unique to these environments.
To get a better overview of all the variables I suggest that you add the possibility to collapse or group the variables by name.
9 votes -
Allow us to use variables in the Package ID field of a template step
We've created a step template for the deploy package step and we made the Package Id a Parameter. This works, until we assign a variable to this field e.g. #{MaintenancePackageId}, in which case the package id doesn't get expanded. The same seems to happen when using the variable directly in the step template without exposing it as a parameter.
The package #{Maintenance_package} could not be located in the built-in repository.
Plus, when using the step template and a parameter, the description of the step shows
"Deploy package #{ParameterPackageId}"
instead of the value being passed in. It does get executed directly…
4 votes -
Warn users when changing main Project Lifecycle when there are Channels
We changed the main lifecycle of the project. The project had a channel defined which was set as the default channel which was using the same lifecycle as the project. There is no indication when changing a project's lifecycle that the underlying channels are not updated, except for a cryptic message below the lifecycle selection which can be read as "There is a small possibility that in certain circumstances someone may have defined a channel, in which case what you see here may not be what is happening in reality. We'd really, really love to get a warning or at…
1 vote -
Full change history for library variable sets
None of the current audit log filters (as of v3.3) make it easy to find changes to library variable sets.
Sometimes a value changes and we don't know why. We like to know who changed it, and how long ago (and whether there have been other changes to that variable in the past). Then we can have an informed conversation about it, with those concerned.
9 votes -
Apply channel restrictions to life cycle phases
Now that we are starting to embrace channels, we are finding that we want to limit which channels can go to which stage in a lifecycle. For instance, we have two channels - master and pull-requests. Pull Request (aka deployment per PR) can only go to the Staging Environment, but the master channel can go to Staging and Production.
Right now we have two life cycles to make this happen, but that causes a lot of extra life cycles.
3 votes -
Rename "Service accounts" to "API Accounts"
The term "Service Account" is massively overloaded in the technology world. It is most commonly used to refer to Active Directory/LDAP accounts used by services, and thus can be very confusing when using the term in communications. Renaming it to "API Account" would help to differentiate it from the accounts the Website runs under.
1 vote -
Make steps collapsable when they contain child steps
When working with larger projects that contain steps within steps, the page refreshes often when making changes so this involves a lot of scrolling to find the steps you are working on. It would be great if you could collapse steps that contain children so there's a smaller list to scroll through.
19 votes -
Allow for teams to be excluded access to environments, not just included
Currently in the Teams area you can either allow team access to All Environments or select which environments they have access to by including them explicitly. It would be great if we could select environments they should be excluded from (UAT, Production, etc).
We're trying to take advantages of Azure and the ability to create test environments on the fly that allow our testers and developers to create environments for them to deploy to. Under the current access rules they need the ability to access all environments (leaving the Environments access field blank) or add each environment as it is…
17 votes -
Multi language support in administration panel
With the introduction of Multi Tenant support, we can allow our customer to acess the administration panel of Octopus Deploy. The barrier that i found to do that, is that the software that i work, provides services with the main language PT-BR. To meet our demand, multi language support is necessary.
1 vote -
Make property values fields in step templates as links
Make property values fields in step templates as links
I wanted to edit properties of step template. The value of property was read only and it wasn't obvious how can I change it.
Finally I noticed that label of property is clickable. The property name doesn't have visual indication(e.g. underline) that it's a link/button.The better UX will be to make value field as link to open the same Edit Property dialog.
Alternatively you can make the value field as an editable textbox to change value inline.1 vote -
Allow SSH Accounts to include SSH Key Pairs w/ Passwords (not just passphrases for the key)
Recently we created an Ubuntu Server that required both a Private SSH Key w/ PassPhrase AND a Password. This failed to connect because it didn't have the password field/value available in the Environment Accounts setup.
Ultimately, we went with just a password for the account, but Octopus should allow for this feature as well.
1 vote -
Clearly show the phases of a lifecycle on the dashboards
The dashboards show each of the environments to deploy to, but they don't indicate which are part of each individual phase of a lifecycle. This means if we need to deploy to one of five environments it can get a little confusing without a really clear environment name.
I propose that we draw a line divider in between the phases or colour the environments within a phase differently from each other.
3 votes -
Add global steps
I have come to find almost all of the project steps for my applications follow a general pattern:
Deploy package
Do clean up
Configure
Send EmailIf I could encapsulate steps similar to Variable sets so that I can include them where needed, this would actually cut down on my maintenance requirements by a ton. I see this as kind of a rules engine. So...
"When a package is deployed..." do a step before the process is allowed to continue.
"When a project is released..." do a step after the process is done.All of these would be able to…
1 vote -
Enable Octopus server to be deployable via machine image
Is it possible to create an AWS AMI using Hashicorp Packer with Octopus server installed? Is there any guidance or documentation? We're finding it a bit difficult.
3 votes -
When entering a new page/form, put the cursor in the first available textbox.
Right now there are quite a few screens/forms which won't place the cursor in the first textbox, making keyboard navigation a mess.
1 vote -
SMTP Implicit SSL
Octopus server currently supports Explicit SSL in it's SMTP Configuration. It would be good if it could also support Implicit SSL.
1 vote -
Allow to send emails using ImplicitSSL next to ExplicitSSL
It's quite easy to achieve using package like this https://www.nuget.org/packages/AIM
1 vote
