• 1
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      When entering the planning mode in the agile board in Greenhopper, the current sprint appears collapsed, while the backlog has no option to either collapse/expand. It's always expanded.

      I'm looking for the possibility to collapse the backlog.

            [JSWSERVER-6908] Collapsable backlog

            olz added a comment -

            I have created a straightforward tool to collapse/expand the backlog in Chrome for personal use, while Atlassian takes care of the issue.

            The name is Jira backlog expander

            olz added a comment - I have created a straightforward tool to collapse/expand the backlog in Chrome for personal use, while Atlassian takes care of the issue. The name is  Jira backlog expander . 

            Hi Tom, you are right, there was a typo in the snippet. I updated the comment with the correct snippet. Please try again.

            Sebastian Patiño-Lang added a comment - Hi Tom, you are right, there was a typo in the snippet. I updated the comment with the correct snippet. Please try again.

            boardtc added a comment - - edited

            Great great idea to solve this with bookmarklets, thanks!!

            I tested the collapsed bookmarklet in v7.1.4 but I get an exception: Uncaught SyntaxError: Unexpected token ). Chrome is restarted having disabled the Grammarly extension too so that should not be related -see issue.

            I also tried in IE 11, which has no Grammarly disabled or otherwise, but nothing happened.

            boardtc added a comment - - edited Great great idea to solve this with bookmarklets, thanks!! I tested the collapsed bookmarklet in v7.1.4 but I get an exception: Uncaught SyntaxError: Unexpected token ). Chrome is restarted having disabled the Grammarly extension too so that should not be related - see issue . I also tried in IE 11, which has no Grammarly disabled or otherwise, but nothing happened.

            Have the same issue.

            As a quickfix I created a bookmarklet that collapses all open sprints in backlog view. Tested on v7.1.6.

            javascript: (function() { $("div.ghx-backlog-container").each(function() {if ($(this).hasClass("ghx-open")) {$(this).find("div.ghx-expander").click();}}); }());

            If you want to expand them all again, here you go:

            javascript: (function() { $("div.ghx-backlog-container").each(function() {if ($(this).hasClass("ghx-closed")) {$(this).find("div.ghx-expander").click();}}); }());

            Sebastian Patiño-Lang added a comment - - edited Have the same issue. As a quickfix I created a bookmarklet that collapses all open sprints in backlog view. Tested on v7.1.6. javascript: (function() { $("div.ghx-backlog-container").each(function() {if ($(this).hasClass("ghx-open")) {$(this).find("div.ghx-expander").click();}}); }()); If you want to expand them all again, here you go: javascript: (function() { $("div.ghx-backlog-container").each(function() {if ($(this).hasClass("ghx-closed")) {$(this).find("div.ghx-expander").click();}}); }());

            Mark Finta added a comment -

            I like to have many different boards with restrictive filters to make sure boards do not have too many issues on them.  But for reporting purposes, you need to have this board that contains all the issues.  Especially for large projects with many teams.  You need the individual teams, but the large board with the 30k issues is required for reporting.  There are also managers that need to have view into these large boards.  There is no reason for them to view 30k issues in the backlog.  Having the ability to collapse the backlog to literally just be able to scroll would be a huge help.

            Mark Finta added a comment - I like to have many different boards with restrictive filters to make sure boards do not have too many issues on them.  But for reporting purposes, you need to have this board that contains all the issues.  Especially for large projects with many teams.  You need the individual teams, but the large board with the 30k issues is required for reporting.  There are also managers that need to have view into these large boards.  There is no reason for them to view 30k issues in the backlog.  Having the ability to collapse the backlog to literally just be able to scroll would be a huge help.

            We usually have around 20 issues to plan for a sprint and 1500+ issues in the backlog. Due to this huge backlog, the browser response gets very slow. It would be good if the backlog can be collapsed. Also a Collapse All button would be helping to immediately view and select/expand the desired sprint.

            Amir Zaka Bhatti added a comment - We usually have around 20 issues to plan for a sprint and 1500+ issues in the backlog. Due to this huge backlog, the browser response gets very slow. It would be good if the backlog can be collapsed. Also a Collapse All button would be helping to immediately view and select/expand the desired sprint.

            I'll be honest. We have 2,717 issues in our backlog. It's a huge drag on the Agile board when trying to scroll up and down, move issues, etc. Would be great to be able to collapse this or paginate it or something...

            David Sendroff added a comment - I'll be honest. We have 2,717 issues in our backlog. It's a huge drag on the Agile board when trying to scroll up and down, move issues, etc. Would be great to be able to collapse this or paginate it or something...

            Ivar added a comment -

            I second this issue - our backlog is huge, and it would be great to be able to expand/collapse it.

            Ivar added a comment - I second this issue - our backlog is huge, and it would be great to be able to expand/collapse it.

            Hi Michael.

            This is a long time ago, and I don't really remember what I was thinking about. I think it was something like this; Our backlog is huge, it contains thousands of Issues. Even though we can filter many of them, it contains somewhere around 4-500 issues. Cheers.

            Benjamin Golba added a comment - Hi Michael. This is a long time ago, and I don't really remember what I was thinking about. I think it was something like this; Our backlog is huge, it contains thousands of Issues. Even though we can filter many of them, it contains somewhere around 4-500 issues. Cheers.

            Thanks for reporting this issue. May I ask why you would like the backlog to be collapsable?

            Thanks,
            JIRA Agile Team

            Michael Tokar added a comment - Thanks for reporting this issue. May I ask why you would like the backlog to be collapsable? Thanks, JIRA Agile Team

              Unassigned Unassigned
              2229b093d04f Benjamin Golba
              Votes:
              27 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - 2h
                  2h
                  Remaining:
                  Remaining Estimate - 2h
                  2h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified