[JENKINS-23492] UI improvements / refreshing

[jenkins-infra-bot]

This is a catch-all JIRA for UI style/layout improvements we're making as discussed on dev thread: https://groups.google.com/forum/?hl=en#!topic/jenkinsci-dev/zDaX4yiWLLw

---

Originally reported by tfennelly, imported from: UI improvements / refreshing

• assignee: tfennelly
• status: Resolved
• priority: Major
• component(s): core
• label(s): user-experience
• resolution: Fixed
• resolved: 2014-08-07T14:39:25+00:00
• votes: 0
• watchers: 5
• imported: 2025-11-24

Raw content of original issue

This is a catch-all JIRA for UI style/layout improvements we're making as discussed on dev thread: https://groups.google.com/forum/?hl=en#!topic/jenkinsci-dev/zDaX4yiWLLw

2 attachments

• Bildschirmfoto 2014-07-12 um 18.33.41.png

  

• Screencast-Flickering.mov

[jenkins-infra-bot]

scm_issue_link:

• Original comment link
• Raw content of original comment:

  Code changed in jenkins
  User: tfennelly
  Path:
   changelog.html
  http://jenkins-ci.org/commit/jenkins/1aec030e0811e9046d2f57395dac98872de715fa
  Log:
    [FIXED JENKINS-23492] UI improvements / refreshing
  
  
  

Code changed in jenkins
User: tfennelly
Path:
changelog.html
http://jenkins-ci.org/commit/jenkins/1aec030e0811e9046d2f57395dac98872de715fa
Log:
[FIXED JENKINS-23492] UI improvements / refreshing

[jenkins-infra-bot]

tfennelly:

• Original comment link
• Raw content of original comment:

  Updated Button styles in 83b54a9
  

Updated Button styles in 83b54a9

[jenkins-infra-bot]

tfennelly:

• Original comment link
• Raw content of original comment:

  Friendlier form controls in d78f26e
  

Friendlier form controls in d78f26e

[jenkins-infra-bot]

tfennelly:

• Original comment link
• Raw content of original comment:

  Tweak to dropdown menu shadow in b1c9c48
  

Tweak to dropdown menu shadow in b1c9c48

[jenkins-infra-bot]

dogfood:

• Original comment link
• Raw content of original comment:

  Integrated in  jenkins_main_trunk #3477
       [FIXED JENKINS-23492] UI improvements / refreshing (Revision 1aec030e0811e9046d2f57395dac98872de715fa)
  
       Result = SUCCESS
  tom.fennelly : 1aec030e0811e9046d2f57395dac98872de715fa
  Files : 
  
  	
  changelog.html
  
  
  

Integrated in jenkins_main_trunk #3477
[FIXED JENKINS-23492] UI improvements / refreshing (Revision 1aec030)

Result = SUCCESS
tom.fennelly : 1aec030e0811e9046d2f57395dac98872de715fa
Files :

• changelog.html

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  Should probably keep this updated with recent changes.
  

Should probably keep this updated with recent changes.

[jenkins-infra-bot]

drulli:

• Original comment link
• Raw content of original comment:

  After the button style upgrade the position of the buttons looks strange. Would be better if we would have some alignment with the text and with all other buttons. 
  
  Moreover: if auto-refresh is activated, then the buttons flicker during the refresh (new style -> default style -> new style). Maybe we should disable auto-refresh for the manage Jenkins page?
  
  Wouldn't it make more sense to have one issue for each UI improvement so we can see which issues are resolved? Maybe we should introduce a new component (user experience) for which we can report such issues. 
  

After the button style upgrade the position of the buttons looks strange. Would be better if we would have some alignment with the text and with all other buttons.

Moreover: if auto-refresh is activated, then the buttons flicker during the refresh (new style -> default style -> new style). Maybe we should disable auto-refresh for the manage Jenkins page?

Wouldn't it make more sense to have one issue for each UI improvement so we can see which issues are resolved? Maybe we should introduce a new component (user experience) for which we can report such issues.

[jenkins-infra-bot]

tfennelly:

• Original comment link
• Raw content of original comment:

  We'll look into that Ulli.  Thanks for letting us know.
  
  I agree with you re creating multiple JIRAs.  I was flipping and flopping between doing it on one JIRA (as we currently are doing) and multiple JIRAs.  I think if we do as you say and introduce a new "user experience" component, then we can use multiple JIRAs more easily.
  

We'll look into that Ulli. Thanks for letting us know.

I agree with you re creating multiple JIRAs. I was flipping and flopping between doing it on one JIRA (as we currently are doing) and multiple JIRAs. I think if we do as you say and introduce a new "user experience" component, then we can use multiple JIRAs more easily.

[jenkins-infra-bot]

scm_issue_link:

• Original comment link
• Raw content of original comment:

  Code changed in jenkins
  User: tfennelly
  Path:
   core/src/main/resources/hudson/model/AllView/noJob.jelly
  http://jenkins-ci.org/commit/jenkins/65d3799f155fe11fe2c86e8be14a929707e9bd9e
  Log:
    JENKINS-23492 Fixed issue where empty welcome page callout block was appearing.
  
  
  

Code changed in jenkins
User: tfennelly
Path:
core/src/main/resources/hudson/model/AllView/noJob.jelly
http://jenkins-ci.org/commit/jenkins/65d3799f155fe11fe2c86e8be14a929707e9bd9e
Log:
JENKINS-23492 Fixed issue where empty welcome page callout block was appearing.

[jenkins-infra-bot]

scm_issue_link:

• Original comment link
• Raw content of original comment:

  Code changed in jenkins
  User: tfennelly
  Path:
   core/src/main/resources/lib/layout/breadcrumbs.css
   core/src/main/resources/lib/layout/breadcrumbs.js
   core/src/main/resources/lib/layout/layout.jelly
   core/src/main/resources/lib/layout/menu_down_arrow2.png
   war/src/main/webapp/css/style.css
  http://jenkins-ci.org/commit/jenkins/a277b73497edf8a0068a41b5a100d0c856782ce4
  Log:
    JENKINS-23492 Fixed auth/login links in top navbar
  
  
  Compare: b598301...a277b73
  
  

Code changed in jenkins
User: tfennelly
Path:
core/src/main/resources/lib/layout/breadcrumbs.css
core/src/main/resources/lib/layout/breadcrumbs.js
core/src/main/resources/lib/layout/layout.jelly
core/src/main/resources/lib/layout/menu_down_arrow2.png
war/src/main/webapp/css/style.css
http://jenkins-ci.org/commit/jenkins/a277b73497edf8a0068a41b5a100d0c856782ce4
Log:
JENKINS-23492 Fixed auth/login links in top navbar

Compare: b598301...a277b73

[jenkins-infra-bot]

tfennelly:

• Original comment link
• Raw content of original comment:

  New general layout using <div>s f277502a83
  Switch underline/non underline on sidebar in c438a5f2ab
  Line up elements in the left side 8057217f1f
  Fixed issue where empty welcome page callout block was appearing in 65d3799
  Fixed auth/login links in top navbar in a277b73
  

New general layout using

s f277502
Switch underline/non underline on sidebar in c438a5f
Line up elements in the left side 8057217
Fixed issue where empty welcome page callout block was appearing in 65d3799
Fixed auth/login links in top navbar in a277b73

[jenkins-infra-bot]

dogfood:

• Original comment link
• Raw content of original comment:

  Integrated in  jenkins_main_trunk #3521
       JENKINS-23492 Fixed issue where empty welcome page callout block was appearing. (Revision 65d3799f155fe11fe2c86e8be14a929707e9bd9e)
  JENKINS-23492 Fixed auth/login links in top navbar (Revision a277b73497edf8a0068a41b5a100d0c856782ce4)
  
       Result = SUCCESS
  tom.fennelly : 65d3799f155fe11fe2c86e8be14a929707e9bd9e
  Files : 
  
  	
  core/src/main/resources/hudson/model/AllView/noJob.jelly
  
  
  
  tom.fennelly : a277b73497edf8a0068a41b5a100d0c856782ce4
  Files : 
  
  	
  war/src/main/webapp/css/style.css
  	
  core/src/main/resources/lib/layout/breadcrumbs.css
  	
  core/src/main/resources/lib/layout/menu_down_arrow2.png
  	
  core/src/main/resources/lib/layout/breadcrumbs.js
  	
  core/src/main/resources/lib/layout/layout.jelly
  
  
  

Integrated in jenkins_main_trunk #3521
JENKINS-23492 Fixed issue where empty welcome page callout block was appearing. (Revision 65d3799)
JENKINS-23492 Fixed auth/login links in top navbar (Revision a277b73)

Result = SUCCESS
tom.fennelly : 65d3799f155fe11fe2c86e8be14a929707e9bd9e
Files :

• core/src/main/resources/hudson/model/AllView/noJob.jelly

tom.fennelly : a277b73497edf8a0068a41b5a100d0c856782ce4
Files :

• war/src/main/webapp/css/style.css
• core/src/main/resources/lib/layout/breadcrumbs.css
• core/src/main/resources/lib/layout/menu_down_arrow2.png
• core/src/main/resources/lib/layout/breadcrumbs.js
• core/src/main/resources/lib/layout/layout.jelly

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  And I thought we were getting rid of extra components… ( https://wiki.jenkins-ci.org/display/JENKINS/2014+JIRA+Components+Refactoring )
  
  Maybe make 'user experience' or 'ux' a label to group these? Would make sense to have these across components (core and plugins) as well.
  

And I thought we were getting rid of extra components… ( https://wiki.jenkins-ci.org/display/JENKINS/2014+JIRA+Components+Refactoring )

Maybe make 'user experience' or 'ux' a label to group these? Would make sense to have these across components (core and plugins) as well.

[jenkins-infra-bot]

tfennelly:

• Original comment link
• Raw content of original comment:

  Not sure I follow your comment.  Anyway... yesterday I create a new label called "user-experience".
  

Not sure I follow your comment. Anyway... yesterday I create a new label called "user-experience".

[jenkins-infra-bot]

drulli:

• Original comment link
• Raw content of original comment:

  Well, that depends on how the default assignee (or component lead) would like to work with such issues. (Which requires that we have a component lead willing to fix all those issues  With a component the issues are automatically assigned. With a label they are not (the label is also a free text field with code completion, e.g. we have ux and user-experience). I just want to be sure that my issues don't get lost in the enormous amount of open core issues.  
  

Well, that depends on how the default assignee (or component lead) would like to work with such issues. (Which requires that we have a component lead willing to fix all those issues With a component the issues are automatically assigned. With a label they are not (the label is also a free text field with code completion, e.g. we have ux and user-experience). I just want to be sure that my issues don't get lost in the enormous amount of open core issues.