# I'm disappointed :( **URL:** \ **Category:** UX SIG\ **Created:** [March 1, 2023, 5:59am UTC](https://community.jenkins.io/t/im-disappointed/6036 "2023-03-01T05:59:11Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![geri](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/geri/32/6934_2.png) [@geri](https://community.jenkins.io/u/geri)\ **Post date:** [March 1, 2023, 5:59am UTC](https://community.jenkins.io/t/im-disappointed/6036/1 "2023-03-01T05:59:12Z")
It’s a while ago that I worked with Jenkins, I’ve always liked it exceptionally, it always was one of the top 3 tools I used and I promoted it whenever I had the chance to. Now that I installed v2.363 I’m disappointed with the UI – a second time: 1. First there were these new flat, boring build status/weather icons, see also [How to get the classic Jenkins build status icons back?](https://devops.stackexchange.com/q/14909/24991). 2. I always liked the idea of the drop-down menus next to the breadcrumbs reachable by always visible(!) ⯆. Now there are thin, harder to recognize \> they are hidden and instead of one click I have to perform a hover, a move, a click. And the click targets change their position dynamically which is distracting. I’m sorry having to say that but that’s bad UX. 3. The colors, shapes and behaviour in general: Jenkins is not a consumer product, it’s a workhorse for DevOps, SREs, Developers, … to get the job done as efficient as possible. Being one of them I don’t need / I don’t want: I’ m disappointed, partly appalled, really. ### UPDATE 1. Re the almost all just black (dark gray?) icons left of the sidebar menu items: 2. Project config: There’s **General** at the top and (just the word) _Enabled_ with ☐/🗹 to the right of it. The tooltip tells me that this applies to the current project, not the **General** config settings. _Project enabled_ 🗹 / _Project disabled_ ☐ would be clearer. ---
**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\ **Post date:** [March 1, 2023, 9:04am UTC](https://community.jenkins.io/t/im-disappointed/6036/2 "2023-03-01T09:04:43Z")
Welcome back to the forum, @geri 👋 Thank you for sharing your feedback regarding the new UI/UX in Jenkins. I do appreciate your support for Jenkins and your dedication to using the tool to its fullest potential. While it may be too late for your specific feedback to be implemented in the current version, I’d like to invite you to participate in our [User Experience SIG meetings](https://www.jenkins.io/sigs/ux/) to provide your feedback directly to some community members that implemented the design of the UI/UX. I think the community’s goal is to create an experience that is as efficient and user-friendly as possible for all users. Your feedback will be valuable in helping achieve that goal, and I am grateful for your input. I understand that change can be challenging, and I want to assure you that the community is always working to improve Jenkins and address end users concerns. Thank you again for your feedback and your continued support of Jenkins. I hope to see you at our next User Experience SIG meeting which happens to be today at **4PM UTC**. **Join [Zoom Meeting](https://www.google.com/url?q=https://zoom.us/j/91788301376?pwd%3Dekh0NWUvNCs1UVNaaGp2SjZydVMxZz09&sa=D&source=calendar&usd=2&usg=AOvVaw2u0hDfqCpMhbheFoWxbToc)** The agenda and minutes can be found at [https://docs.google.com/document/d/1QttPwdimNP\_120JukigKsRuBvMr34KZhVfsbgq1HFLM/edit#](https://www.google.com/url?q=https://docs.google.com/document/d/1QttPwdimNP_120JukigKsRuBvMr34KZhVfsbgq1HFLM/edit%23&sa=D&source=calendar&usd=2&usg=AOvVaw2TMsB6a_81xNHKym-cjXGT) Chat is available on Gitter: [https://gitter.im/jenkinsci/ux-sig](https://www.google.com/url?q=https://gitter.im/jenkinsci/ux-sig&sa=D&source=calendar&usd=2&usg=AOvVaw3JbVwrNDl6iqTokrkn7CIH) ---
**Author:** ![uhafner](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/uhafner/32/68_2.png) [@uhafner](https://community.jenkins.io/u/uhafner)\ **Post date:** [March 1, 2023, 9:56am UTC](https://community.jenkins.io/t/im-disappointed/6036/3 "2023-03-01T09:56:33Z")
Thanks for sharing your feedback! I’m not sure if I can comment all points in your list so I start with some general comments. I think the new UI changes in the latest LTS versions are a huge improvement, making Jenkins attractive again. But I also see that some of these changes are not ideal for everybody (please also see [New UI, form spacing and poor usability](https://community.jenkins.io/t/new-ui-form-spacing-and-poor-usability/3885)): 1. Some layout changes are a matter of taste and should be part of the Jenkins theming engine. 2. Some changes are controversial and cannot be changed by a theme. 3. Some changes are not yet finished and need to be fixed in the future. 4. Plugins need to use the new concepts as well. For 1., 3., 4. we currently have the problem that actually only a couple of Jenkins developers are left over and no new volunteers step up to actually help to make the user experience better. I also noticed this in my own plugins as well: nobody steps up to actually fix a problem anymore - even for simple one hour tasks. For 2. I think it would make sense to either create an issue in Jira or bring the topic to the UX meeting. E.g.: > 1. I always liked the idea of the drop-down menus next to the breadcrumbs reachable by always visible This is also a UI change that IMHO provides a bad user experience, especially when using in conjunction with [Update link dropdown menus to use new Tippy dropdowns by janfaracik · Pull Request #7474 · jenkinsci/jenkins · GitHub](https://github.com/jenkinsci/jenkins/pull/7474). Maybe this is a good point for the UX meeting today? The same should be done for a lot of your other points. ---
**Author:** ![timja](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/timja/32/7_2.png) [@timja](https://community.jenkins.io/u/timja)\ **Post date:** [March 12, 2023, 10:45pm UTC](https://community.jenkins.io/t/im-disappointed/6036/4 "2023-03-12T22:45:42Z")
FYI there’s a pull request here for the legend moving to the same page: > > > \image > > \* Introduces a new lightweight modal component (currently lacking in depth, but eventually it could be used for confirmation dialogs, notices etc) > \* Replaces the icon legend page with an accessible modal > > \### Testing done > > \* Icon legend works the same as before > > \### Proposed changelog entries > > \- Revamp icon legend as a modal > > \### Proposed upgrade guidelines > > N/A > > \### Submitter checklist > > \- \[\] The Jira issue, if it exists, is well-described. > \- \[\] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see \[examples\](https://github.com/jenkins-infra/jenkins.io/blob/master/content/\_data/changelogs/weekly.yml)). > - Fill in the \*\*Proposed upgrade guidelines\*\* section only if there are breaking changes or changes that may require extra steps from users during upgrade. > \- \[\] There is automated testing or an explanation as to why this change has no tests. > \- \[\] New public classes, fields, and methods are annotated with \`@Restricted\` or have \`@since TODO\` Javadocs, as appropriate. > \- \[\] New deprecations are annotated with \`@Deprecated(since = "TODO")\` or \`@Deprecated(forRemoval = true, since = "TODO")\`, if applicable. > \- \[\] New or substantially changed JavaScript is not defined inline and does not call \`eval\` to ease future introduction of Content Security Policy (CSP) directives (see \[documentation\](https://www.jenkins.io/doc/developer/security/csp/)). > \- \[\] For dependency updates, there are links to external changelogs and, if possible, full differentials. > \- \[\] For new APIs and extension points, there is a link to at least one consumer. > > \### Desired reviewers > > @jenkinsci/sig-ux > > \