Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-64834

Buttons are too big

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Similar Issues:

      Description

      First off this tracking system for tracking sucks. What's up with all the 'read this' in red BS? and how the F am I supposed to know what component? 

      Second, upgraded to the latest version of Jenkins. The left buttons are WAY bigger now. They look nicer, but who said "please make them bigger?" no one. They now push important information off the bottom. Please spend less time making it look pretty and more time making it more useful.

      How about a different icon for Edit View and Manage Jenkins. Come on. A gear? That's a total punt. How about a gear for each menu item?

      Or how about another icon that's a screw driver and a wrench?

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          The "read this" entries are provided in the hopes that you'll understand that an issue report to the Jenkins issue tracker is an attempt by the submitter (you) to persuade volunteers (like me) to give some of their time to understand your concern.

          An issue report is weighed by volunteers against other issue reports and against other ways they might spend their time. Using inconsiderate or harsh language does not increase your chances of persuading volunteers to assist you with their time or their skills.

          The "How to report an issue" page provides guidelines for techniques that can increase the chances that you'll persuade volunteers to invest their time to assist you.

          If you are interested in page layout and design, then an even better way to be involved is to submit pull requests that propose the changes you believe will help Jenkins. The Jenkins user experience special interest group is ready to have more people assist them with user interface improvements. They would be glad to have more design and code contributions to assist with the UI improvements.

          Show
          markewaite Mark Waite added a comment - The "read this" entries are provided in the hopes that you'll understand that an issue report to the Jenkins issue tracker is an attempt by the submitter (you) to persuade volunteers (like me) to give some of their time to understand your concern. An issue report is weighed by volunteers against other issue reports and against other ways they might spend their time. Using inconsiderate or harsh language does not increase your chances of persuading volunteers to assist you with their time or their skills. The "How to report an issue" page provides guidelines for techniques that can increase the chances that you'll persuade volunteers to invest their time to assist you. If you are interested in page layout and design, then an even better way to be involved is to submit pull requests that propose the changes you believe will help Jenkins. The Jenkins user experience special interest group is ready to have more people assist them with user interface improvements. They would be glad to have more design and code contributions to assist with the UI improvements.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            sbroshar steve
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: