|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Yes, Daniel I am aware of the faulty logic underlying the decision to not put these links on sub pages of the job, but restating that faulty logic does not make it valid. They are not completely different objects, they are sub objects of each other. Sure there should be some differentiation in the links between the actions to take at the job level and the sub page level but that does not justify removing the job level links. And no having to do target practice to hit that tiny little triangle to open up a submenu to then see the actions and click yet again is not good enough.
Any level of usability testing would show that Build Now and Configure are the most often used actions taken on any job, followed by see the console of the latest build. Luckily we have plugins like extra columns which lets up put those actions directly on the dashboard but navigating within a job to these actions is still a pain.