4 ms·

This is really useful feedback @Karunamon! I see Sarrah already addressed it so I just wanted to add my bit: I also think that the approach we used for designin

This is really useful feedback @Karunamon! I see Sarrah already addressed it so I just wanted to add my bit: I also think that the approach we used for designing settings pages isn't optimal and suggested improvements in a discussion on a related issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/45219 https://gitlab.com/gitlab-org/gitlab-ce/issues/45219 After seeing your feedback (and confirming my assumption) I decided to open a new issue to specifically address this and would love to get your feedback on the proposed solution: https://gitlab.com/gitlab-org/gitlab-ce/issues/47405 https://gitlab.com/gitlab-org/gitlab-ce/issues/47405 Thanks again for taking the time to write such detailed feedback down. It's really helpful to us. Cheers!

frakman1 8y ago
I agree that the Settings page is a pain to use or find anything. I prefer everything to be displayed in one page so I can do a quick Cnt+F and search for the string I am looking for instead of tediously mousing over every button to expand. See Jenkins->Manage Jenkins->Configure System
- Karunamon 8y ago
  Oddly enough, I stumbled on the fact that Ctrl-F works fine on these pages. All of the items below the expands are still visible to the search, and the expand automatically pops open when your cursor jumps to the matching text.