Re-think the new UI! It is awful!!!
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.
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.
In case you want to go to the old UI, you can access it here: https://octo.yoursite.com/oldportal#/
Make sure to login first or you'll see an authentication error
The beauty of Octopus was that it was easy to configure and use. Unfortunately, with the UI update I feel that you have taken several steps backwards. I have had to spend some time figuring out how things work with the new UI and it is frustrating. Bring back the old UI.
Joel Greijer commented
If you have more than nine projects in a project group, and more than 5 environments, the gui makes it impossible to work in dashboard mode. You end up in "scrollbar hell" :-)
Tim Wattley commented
@William Hughes: I agree 100%. It's probably my biggest annoyance with the new UI (re-deploying to the same environment).
I'm happy to hear they're aware and working on it.
I've been using Octopus on daili basis for last four years.
I usually do not waste time to post such feedback but this time i jsut cant pass by...
New UI is horrible.
When I've been deciding to use Octopus over other solution key point was not only features but also clarity and interface simplicity.
I've been trying few other solutions and UI was not that good (at that time).
Right now i wouldnt pickup Octopus for this single purpose - UI.
Please rethink places like "create release" and "process configuration", use some colors for sections(now its one big wall of "not sure if its clickable" labels).
One good thing is that UI is way faster now. Tho i would sacrifice this anytime to get back "clear" UI...and not to mention that spinners are sometimes wrongly aligned(that just minor but looks unprofessional)
Hopefully we will see some improvements in next releases
Doron Neumann commented
I hate the new UI.
Deployments I would accomplish with 1 click now take 3 or 4 browsing through dropdown menus.
Whoever designed this UI clearly does not use Octopus deploy.
Thanks for your comment @William. That particular issue is one that we are aware of and is bubbling up to the top of our list of priorities. Thanks again!
William Hughes commented
I'm not sure whether this should be as a seperate issue - but I do agree that while there's certain aspects of "They moved my cheese" - it has made certain tasks much more difficult to do.
Yesterday I spent nearly 30 minutes trying to figure out how to re-deploy the same release to an environment (something I do on a semi-regular basis when adding new machines to an environment).
It used to be two or three clicks from the dashboard - click the released version in that environment, click 'Promote To' or 'Deploy To' (I forget which) and then select which environment and target(s) to deploy to.
Now, from the dashboard I click on the release version, click back to Releases, click on the release version again, and then I can click the dotted drop down to get a 'Deploy To' option.
It's not easily discoverable.
Thank you for taking the time to reply. I figured I would be in the minority here as I have very strong opinions on UI and design. I truly appreciate company's that take the time to update their UI's if it truly makes for a better product. Many would never take that time to do this type of work. I also appreciate that you updated your documentation. With that said, you are still missing how to do some things, i.e adding a new variable. With over Twenty years of development experience, I have seen a lot of good and bad examples of user interfaces. While we are not running 1000's of deployment projects, we are running over 50 so having an intuitive and easy to read UI is very important to us. Unfortunately, this UI update has cost my company a fair amount of money in lost productivity while we learned your new UI. I was not aware of the UI update that was planned for version 4 so I was surprised by the drastic redesign. I am not sure how you notified your user base of this update for review but I do not recall seeing that notice. So these may be late, but please take these thoughts into consideration moving forward.
With the rise of mobile devices, it has created a UI problem for websites with how to handle desktop vs. mobile. In other words the big screen vs the small screen. What works for one may not work well for the other. You have used a fair number of components in your redesign that are used in mobile UI's. They work great with the lack of screen real estate on small touch-based screens, but I find these components problematic on larger desktop screens. On the subject of consistency, it is great but consistency over usability is not good. Consistency over usability is a dogmatic approach to UI design. Plus I don't think you are being as consistent as you think you are, i.e. The vertical ellipse button for actions does not contain all the actions possible for some of your interfaces. As an example, I have found the UI for managing variables to be all over the place for functionality and the most difficult to use (my opinion). I have asked other developers in our company to try the UI and most struggled to figure out how to do some of the actions for adding and updating variables. They liked the overall look but had issues with the usability. But to be fair, tabular UI's for this type of parent/child configuration data is never going to be great and are very difficult to make work. Using a UI library is helpful for creating a nice look and feel but does not automatically mean that the functionality is appropriate. The selection of components should be based on the requirements and not a strict view forcing the use of components (in other words, this is cool where can I use it). Again my opinion, but I think you may have missed the point of Material Design in favor of using a React component library.
I have said enough. Again, thank you for your reply and the time to take my thoughts into consideration. No need to reply to this or post it.