-
Add the ability to disable specific environments to all but system administrators
When we're doing mass maintenance to an entire environment, it would be useful to be able to disable non-admins from doing things to that environment, and display a banner (e.g."Deployments to production are disabled while servers are being re-racked") without stopping activity in other environments.
Looking for something much like the system-wide maintenance mode, except environment specific.
6 votes -
Add last date modified field to Variable Views
Add a last date modified field on variables. I think it would be very useful, so it's evident where regression may have occurred between releases and so on if someone makes an update in a group access setting. I know the audit table is useful in this regard, but takes significantly more digging to parse. If you really want to get fancy, show the date, and then if you click it, an audit popup of the last n times it was edited, what date, and by whom.
6 votes -
Support changing channel version rules and/or tags with octo.exe
We have quite a few channels. We also create a new feature branch for each feature we develop. It would be nice if I could script changing the version rules and tags via a script instead of the UI.
6 votes -
Add the ability to exclude projects from users, instead of the current include
Currently in the Teams area you can restrict that team to certain projects, be selecting certain projects. But if new projects are added you have to include those new projects. It would be nice to be able to exclude a team from projects so new projects are automatically allowed.
Also would be nice to include (current) and/or exclude (above idea) project groups as well.
In our environment we need to allow access to all projects except 5.
6 votes -
multi-line input box for variables in step templates
When you create step template and set up variables, you can choose multi-line text box.
But you cant use default value with many rows because input row "Default value" is single-line6 votes -
Associate Variable Sets to Projects
By default, a Variable Set should apply to all projects, but it would be nice to be able to associate it to a specific set of projects.
In our team, we have 13 projects that share a variable set. There's currently no way to restrict our users to only have access to those variables without having the same access to other variable sets for other parts of our organization. We don't want to have to duplicate those variables 13 times.6 votes -
Allow option to export/import Project Steps Only
We are using multiple servers and want to export/import project steps between them. Right now the environments, machines, roles ..etc must match and the variables gets overwritten to import.
An option to export/import project steps ONLY (and via GUI) will be greatly appreciated.
For example, if we have a server for QA, then prosecution, which clearly have different environments ..etc, we want to be able to import/export between these.
6 votes -
Restrict a machine to only specific enviroment
I am an administrator and I manage 3 environments DEV/QA/PROD. After I install Tentacle in a prod server, I should be able to add that machine only under production environment.
One way to do is by having a different thumbprint for each of the environments.
6 votes -
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 -
Include description field for project and library set variables similar to project template variables
It would be helpful to have a description field for variables in a project or in library set variables. I know the idea of having 'descriptive variables' usually solves this issue but sometimes across teams it doesn't always happen.
To save screen space it could be a descriptor you enter when making the variable then when you mouse over the variable it shows the information descriptor.
5 votes -
Separate permissions in the User Role "Project Contributor"
Currently, in order to allow developers to access and edit variables, they are also able to edit process steps including disabling them. This means that they are able to disable audit steps before deploying.
If process edit was a separate permission we could split out the ability to edit variables and the ability to edit/change process steps
5 votes -
Add security secret cleansing to Artifacts
When Octopus attaches Artifacts it does not screen the for any secrets or credentials as such these can often compromise accounts etc that are used to create that Artifact, depending on what it is and how its made.
It would be great if before Octopus attached the Artifact it looked to screen and cleanse the Artifact of potential Secrets there fore reducing the risk of it been used for security exploits etc.
5 votes -
Expand All GUI by default
Have a checkbox in v4.x in the users profile to default expand all. This is the biggest visual shift from 3.x to 4.x, is the collapsing of content.
5 votes -
Implement "next step" and "previous step" buttons
The idea is to have two buttons on the top of our process steps which allows navigating easily between steps process.
5 votes -
Allow audit items to display the actual Date/Time
Currently the audit screen only shows when an item was deployed or changed with 'x days ago', 'x minutes ago' etc.
It would much more useful to able to provide this information to an auditor (say when undergoing a SOC II audit) if this was the actual date/time.
5 votes -
Allow Teams to have a Team Administrator
Currently only Octopus Administrators have permissions to update team membership.
We should be able to elevate users to Team Admins for that team which would allow them to only update the membership of that team.
5 votes -
Allow script modules to be uploaded from a package
Script modules need versioning and be under source control to fully control them,
I want to upload a package and make a call to Octo that would instruct it to create a new Script Module or to update a given Script Module with the script(s) in that package
5 votes -
Filter Environments Shown on Project Overview Page
When I navigate from the dashboard to the Project Overview page, the page should only show the environments that I selected on the Configure Dashboard screen. Also, it would be helpful to filter the list of environments by channel or lifecycle.
5 votes -
Support sorting projects and project groups
At the moment there is no way to define order for projects or project groups.
This would be handy for all sorts of reasons but most significantly on the dashboard
5 votes -
Increase the width of the project name cell on the Dashboard
This is only a small CSS change but if you could increase the width of the "cell" that contains the project name on the dashboard that would be great. We have lots of screen space but project names (and group names) are wrapping after just 20 odd characters.
5 votes
- Don't see your idea?