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

Pagination for Summary tabs

XMLWordPrintable

    • 1.0-m10, 1.0-m12, 1.0-pre-beta-1, 1.0-beta-1

      In Scope

      • When there is more data beyond the first page show the "Show More button"
      • If there is no data beyond the page then hide the "Show more button"
      • Clicking "show more" updates the history so that any refreshes or use of the back button keeps the page and scroll position

          [JENKINS-35788] Pagination for Summary tabs

          James Dumay added a comment -

          Can you help guide this contributor towards the right solution? https://github.com/jenkinsci/blueocean-plugin/pull/221

          James Dumay added a comment - Can you help guide this contributor towards the right solution? https://github.com/jenkinsci/blueocean-plugin/pull/221

          James Dumay added a comment -

          Can you help guide this contributor towards the right solution? https://github.com/jenkinsci/blueocean-plugin/pull/221

          James Dumay added a comment - Can you help guide this contributor towards the right solution? https://github.com/jenkinsci/blueocean-plugin/pull/221

          Cliff Meyers added a comment -

          jdumay would like a few more details around requirements first if possible:

          1. Are we limiting the first page to show only 5 rows? Or is this dependent on the user's resolution / window size? The latter is possible but will be quite a bit more work.
          2. If it's based on screen size, had we considered any other approaches such as "infinite scroll" instead? (scroll to bottom, small loader displays while data loads, screen repaints with additional rows

          Based on your response I'll provide feedback to the PR tomorrow.

          Cliff Meyers added a comment - jdumay would like a few more details around requirements first if possible: Are we limiting the first page to show only 5 rows? Or is this dependent on the user's resolution / window size? The latter is possible but will be quite a bit more work. If it's based on screen size, had we considered any other approaches such as "infinite scroll" instead? (scroll to bottom, small loader displays while data loads, screen repaints with additional rows Based on your response I'll provide feedback to the PR tomorrow.

          James Dumay added a comment -

          I'd like to figure out what the optimal page size would be a bit later.
          Could we make it 25 by default and then we can tweak?

          Had considered infinite scroll a while back and the developers I canvased
          didn't like that kind of iteration.
          On Thu, 2 Jun 2016 at 1:36 PM, Cliff Meyers (JIRA) <

          –
          James Dumay
          Product Manager
          CloudBees, Inc.
          Skype: jdumaycb Twitter: i386

          James Dumay added a comment - I'd like to figure out what the optimal page size would be a bit later. Could we make it 25 by default and then we can tweak? Had considered infinite scroll a while back and the developers I canvased didn't like that kind of iteration. On Thu, 2 Jun 2016 at 1:36 PM, Cliff Meyers (JIRA) < – James Dumay Product Manager CloudBees, Inc. Skype: jdumaycb Twitter: i386

          Cliff Meyers added a comment -

          25 sounds good.

          Cliff Meyers added a comment - 25 sounds good.

          James Dumay added a comment -

          Please pick up the linked pagination ticket if you work on this.

          James Dumay added a comment - Please pick up the linked pagination ticket if you work on this.

            kzantow Keith Zantow
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: