To be honest I am not sure why you changed your UI. Other than a bug when adding variables, it was fairly good. My suggestion is that you need to put a lot more time into your UI. The UI for version 4 is awful, sorry but it is and the version 3 was much easier to use. It took me an hour to figure out that what I thought was a table header for the variable list was how you add a new variable, was not clear it was an input form. You hide way too many things, took me twenty minutes to find the delete for an environment. You are forcing lower case now on target names. Very little of the new UI is intuitive. New infrastructure section is hard to find stuff and no breadcrumbs to go back. The list of bad UI just goes on. Stop trying to be clever and just show the info. As a web developer and the person that manages our deployments, I do not care about a fancy React UI that makes my job harder because a designer thought it would be cleaner. Never assume what you think is obvious is to someone else. In time I will figure out the new UI but that is the problem, I have to figure it out.
To be honest I am not sure why you changed your UI. Other than a bug when adding variables, it was fairly good. My suggestion is that you need to put a lot more time into your UI. The UI for version 4 is awful, sorry but it is and the version 3 was much easier to use. It took me an hour to figure out that what I thought was a table header for the variable list was how you add a new variable, was not clear it was an input form. You hide way too many things, took…45 votes
Specific bugs should be forwarded to firstname.lastname@example.org and specific suggestions should have their own thread. There are various open tickets we have created to help address some of the UX concerns (https://github.com/OctopusDeploy/Issues/labels/area%2Fusability). Thanks for everyone’s input, we are continuing to improve the UI based on the constructive feedback provided.
There is a bug in v4.1.7 on the steptemplates/ActionTemplates-7/usage page.
When viewing usage for a step template, the page displayed 'This template has not been used by any projects yet.'
But when I attempted to delete it, I was warned that the template was used by a whole list of projects. I don't have access to those projects, so I suspect that the usage page is only reporting on usage within projects that I have visibility over.
I'm not sure that I could have actually deleted the template, but it would be better if the usage page checked all projects.2 votes
This is currently by design. The deletion check also needs to look at deployment processes that have snapshotted (i.e. deployments still in the system and not cleaned up by retention policy) however this operation can be expensive so it was best left for checking when the action is attempted rather than every time that page is loaded.
since I thoughtlessly upgraded to Version 4.0.x I cant use the GUI in an intuitive way any more.
Such a "touchy" shit everywhere, :-((1 vote
Read title5 votes
Currently setting up IIS is part of the Deploy Nuget Package step and so are a few other config steps.
It would be useful to be able to have setting up IIS, and other config, as a separate step. That way you can view the steps performed clearly and do something if that specific part fails.1 vote
It should be possible to import users from AD rather than having to wait for them to login for the first time before you can assign them to a team. We have already AD enabled our server.
As an extra feature, it would be nice if groups used in teams are resolved. That would mean it is possible to see the effective set of members when configuring the team.1 vote
Showing users in AD that aren’t in Octopus is a little bit backwards to the way our auth system works at the moment. In some of the later work around AD integrations you can now use AD teams as a permission object in Octopus to ensure that as soon as they do log in, they have the appropriate permissions already available
When a dashboard filter is applied, it remains set until cleared.
Once I have filtered the dashboard, I might open multiple projects based on that filter. When I return the dashboard, I would like my previous filter to be retained so I do to re-filter to see the next project0 votes
Editing the dashboard filter sets updates the URL, when you click “Back” (as opposed to navigating to dashboard again) the same filters should still be applied
- Don't see your idea?