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

Improve empty states

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • core
    • None
    • 2.258

    Description

      The empty states look old and dated and are not extensible. The goal of this ticket is create styles that allow for new sectioned empty state blocks that are responsive. They would also set up the possibility to add new empty states programatically by adding a new extension point.

       

      Design brief

       

       

       

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          drulli Ulli Hafner added a comment -

          Can this new screen disabled with a property? Or is there a plan to support this new feature in ATH? Currently all my ATH tests fail if I bump the LTS version from 2.249 to 2.263.

          drulli Ulli Hafner added a comment - Can this new screen disabled with a property? Or is there a plan to support this new feature in ATH? Currently all my ATH tests fail if I bump the LTS version from 2.249 to 2.263.
          fqueiruga Félix Queiruga Balado added a comment -

          So far these changes were for defaults. May I ask how the tests are failing? I can't recall any other ATH failure related to this change.

          fqueiruga Félix Queiruga Balado added a comment - So far these changes were for defaults. May I ask how the tests are failing? I can't recall any other ATH failure related to this change.
          drulli Ulli Hafner added a comment -

          Hmm, maybe my failures are related to something different in 2.263.1. When those test broke in the first time I open the screenshot of the failure and that failure showed the new dialog of this issue.

          When I now look at these failures the reason is something different:

          drulli Ulli Hafner added a comment - Hmm, maybe my failures are related to something different in 2.263.1. When those test broke in the first time I open the screenshot of the failure and that failure showed the new dialog of this issue. When I now look at these failures the reason is something different: https://github.com/jenkinsci/git-forensics-plugin/pull/210 https://github.com/jenkinsci/warnings-ng-plugin/pull/738 It seems that after entering the Pipeline script in the new pipeline dialog, the ok button is pressed automatically (enter key?) and the dialog is closed. Then the next step is failing because the save button is not available anymore.

          People

            Unassigned Unassigned
            fqueiruga Félix Queiruga Balado
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: