Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-6951

As a Scrum Master I would like a horizontal scrollbar on greenhopper Rapid Board

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • 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.

      As a Scrum Master I would like a horizontal scrollbar on GreenHopper Rapid Board as if you add too many columns on a board you don't get a scrollbar which makes each column progressively thinner (and eventually unusable).

        1. IMAG0014.jpg
          756 kB
          Peter Sinkovic
        2. jiraAgileKanban.jpg
          80 kB
          Peter Sinkovic
        3. ScrollOff.png
          198 kB
          Prem Chudzinski [extensi]
        4. ScrollOn.png
          162 kB
          Prem Chudzinski [extensi]

            [JSWSERVER-6951] As a Scrum Master I would like a horizontal scrollbar on greenhopper Rapid Board

            Current state of affairs renders boards unusable, potential deal breaker for us.

            Rick Jones added a comment - Current state of affairs renders boards unusable, potential deal breaker for us.

            Prem Chudzinski [extensi] added a comment - Done as part of the Agile Board Filter for JIRA Software 2.0

            Timothy Lehnen added a comment - - edited

            In this related issue - https://jira.atlassian.com/browse/GHS-3690?focusedCommentId=746696&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-746696 - I've provided a gist based on various workarounds provided by those in this thread and others with a javascript hack embeddable in the Announcement Banner area that can:

            • toggle columns
            • allows them to scroll horizontally
            • allows you to dynamically resize column width

            All of these states are preserved in local storage and the hack is intelligent across rapid boards about the state of columns with the same names. I hope it helps others who are frustrated by the lack of these features.

            Timothy Lehnen added a comment - - edited In this related issue - https://jira.atlassian.com/browse/GHS-3690?focusedCommentId=746696&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-746696 - I've provided a gist based on various workarounds provided by those in this thread and others with a javascript hack embeddable in the Announcement Banner area that can: toggle columns allows them to scroll horizontally allows you to dynamically resize column width All of these states are preserved in local storage and the hack is intelligent across rapid boards about the state of columns with the same names. I hope it helps others who are frustrated by the lack of these features.

            I have cloned this ticket ( https://jira.atlassian.com/browse/GHS-10114 ) where I provided a workaround involving CSS adjustments as promised. Far from ideal but at least it allows us to wait for a potential fix on JIRA side.

            Nestor Urquiza added a comment - I have cloned this ticket ( https://jira.atlassian.com/browse/GHS-10114 ) where I provided a workaround involving CSS adjustments as promised. Far from ideal but at least it allows us to wait for a potential fix on JIRA side.

            Nestor Urquiza added a comment - - edited

            Mapping the value stream as is, is a starting point for any organization introducing Kanban.

            Culture can be built with time and hopefully todo-done are the only columns but as we know that is an idealistic scenario.

            When you have identified a higher defect ratio because there is a step in the process like code review which is missing you cannot ignore the need to add such column which might translate in two columns if you do BA specs review and Developers code review. It could even translate to three columns if you have PMs who are reviewing their work when scoping a project.

            So having a board that accepts scrolling is a definitely need. I will work with our Front End Engineer to make sure we come up with some CSS adjustments that can be loaded using Tampermonkey / Greasemonkey.

            At that point to implement this feature all JIRA Agile would need is to provide a flag that activates scrolling or not based on user preferences or probably just leave the scrollbar for all cases.

            Nestor Urquiza added a comment - - edited Mapping the value stream as is, is a starting point for any organization introducing Kanban. Culture can be built with time and hopefully todo-done are the only columns but as we know that is an idealistic scenario. When you have identified a higher defect ratio because there is a step in the process like code review which is missing you cannot ignore the need to add such column which might translate in two columns if you do BA specs review and Developers code review. It could even translate to three columns if you have PMs who are reviewing their work when scoping a project. So having a board that accepts scrolling is a definitely need. I will work with our Front End Engineer to make sure we come up with some CSS adjustments that can be loaded using Tampermonkey / Greasemonkey. At that point to implement this feature all JIRA Agile would need is to provide a flag that activates scrolling or not based on user preferences or probably just leave the scrollbar for all cases.

            I fully share the concerns by Peter. And I do not think that columns collapsing will solve the issue. Splitting into more boards is pretty annoying and not useful to see the big picture.

            I would strongly suggest to reopen this task and provide us optional feature to enable horizontal scrolling!
            The Kanban columns/valuestream building are very basic now and definitely need more touch.

            Ivaylo Stanev added a comment - I fully share the concerns by Peter. And I do not think that columns collapsing will solve the issue. Splitting into more boards is pretty annoying and not useful to see the big picture. I would strongly suggest to reopen this task and provide us optional feature to enable horizontal scrolling! The Kanban columns/valuestream building are very basic now and definitely need more touch.

            Hi Michael,

            Thank you for a quick response. Let me share again some more notes, which might be useful not just for JIRA Agile Team, but also for others that will find this post.

            One of the Kanban board's strengths is visibility that it is providing (and many more of course). For this reason I am honestly persuaded that collapsing is not the best option. There are no less or more important columns. Kanban is a "production line" and as such, there is no place for a switch which will bring some of the "rooms" to parallel universe for some time.

            Suggestions you provided are useful. Please see my comments:

            • You have seven groups of columns which contain two columns - In Progress and Done. Have you tried collapsing these pairs of columns into one column? You could visually differentiate between the In Progress and Done statuses using Card Colours or Flagging.
              • Some Kanban theory: IP/Done is there on purpose. This way you can collect better metrics. E.g. time that you really spent working on issue, time that it was waiting to be taken to next column, etc. These metrics do really help. Both columns should have limits too. This way you can see if there is bottleneck in the current column or the next one. Flagging would do the trick without using limits and metrics, but that would cripple the process.
            • What does the board look like if you decrease the font size in your browser? Is it legible?
              • To some point, this is ok. 23“ monitor, it was still kinda readable with font 6-8, but also kinda annoying. For boards with less than 12 columns its sufficient.
            • Would it be feasible to split this one board into two or more, each covering a subset of the columns?
              • Honestly, I was not considering it as an option before and it might work. I changed it and I will see how teams will respond to such solution. This is a good workaroud as I can use the statuses to link last column of the first board to the first column of the second one. Maybe you should sell this as a feature till you figure out how to have it in one board
            • Is this board used primarily:
              • as an "information radiator" (read-only status gathering),
              • by all team members to update status, or
              • both?
                • both and more

            Hope this helps somebody,
            Peter
            LinkedIn profile

            Peter Sinkovic added a comment - Hi Michael, Thank you for a quick response. Let me share again some more notes, which might be useful not just for JIRA Agile Team, but also for others that will find this post. One of the Kanban board's strengths is visibility that it is providing (and many more of course). For this reason I am honestly persuaded that collapsing is not the best option. There are no less or more important columns. Kanban is a "production line" and as such, there is no place for a switch which will bring some of the "rooms" to parallel universe for some time. Suggestions you provided are useful. Please see my comments: You have seven groups of columns which contain two columns - In Progress and Done. Have you tried collapsing these pairs of columns into one column? You could visually differentiate between the In Progress and Done statuses using Card Colours or Flagging. Some Kanban theory: IP/Done is there on purpose. This way you can collect better metrics. E.g. time that you really spent working on issue, time that it was waiting to be taken to next column, etc. These metrics do really help. Both columns should have limits too. This way you can see if there is bottleneck in the current column or the next one. Flagging would do the trick without using limits and metrics, but that would cripple the process. What does the board look like if you decrease the font size in your browser? Is it legible? To some point, this is ok. 23“ monitor, it was still kinda readable with font 6-8, but also kinda annoying. For boards with less than 12 columns its sufficient. Would it be feasible to split this one board into two or more, each covering a subset of the columns? Honestly, I was not considering it as an option before and it might work. I changed it and I will see how teams will respond to such solution. This is a good workaroud as I can use the statuses to link last column of the first board to the first column of the second one. Maybe you should sell this as a feature till you figure out how to have it in one board Is this board used primarily: as an "information radiator" (read-only status gathering), by all team members to update status, or both? both and more Hope this helps somebody, Peter LinkedIn profile

            Hi peter.sinkovic2,

            Thanks for providing some insight into your usage of our Kanban boards. We are aware that some Kanban use cases such as "split columns" are not optimally catered for today.

            We are considering solutions that will help with your situation, however horizontal scrolling is not currently one of them (which is why I resolved this issue). One of these solutions is GHS-3690 - the ability to collapse columns.

            Some other potential work-arounds for your situation:

            • You have seven groups of columns which contain two columns - In Progress and Done. Have you tried collapsing these pairs of columns into one column? You could visually differentiate between the In Progress and Done statuses using Card Colours or Flagging.
            • What does the board look like if you decrease the font size in your browser? Is it legible?
            • Would it be feasible to split this one board into two or more, each covering a subset of the columns?
            • Is this board used primarily:
              • as an "information radiator" (read-only status gathering),
              • by all team members to update status, or
              • both?

            Thanks again for your feedback,
            JIRA Agile Team

            Michael Tokar added a comment - Hi peter.sinkovic2 , Thanks for providing some insight into your usage of our Kanban boards. We are aware that some Kanban use cases such as "split columns" are not optimally catered for today. We are considering solutions that will help with your situation, however horizontal scrolling is not currently one of them (which is why I resolved this issue). One of these solutions is GHS-3690 - the ability to collapse columns. Some other potential work-arounds for your situation: You have seven groups of columns which contain two columns - In Progress and Done. Have you tried collapsing these pairs of columns into one column? You could visually differentiate between the In Progress and Done statuses using Card Colours or Flagging. What does the board look like if you decrease the font size in your browser? Is it legible? Would it be feasible to split this one board into two or more, each covering a subset of the columns? Is this board used primarily: as an "information radiator" (read-only status gathering), by all team members to update status, or both? Thanks again for your feedback, JIRA Agile Team

            Dear Michael, despite the (unfortunate) statement about not including this feature, let me attach a screenshot of a physical kanban board we are using, so you can see the "real thing". We wanted to start using kanban boards in jira (mostly because tracking time / metrics), but its not really possible when you cant see anything on board (tested on 23" widescreen monitor). Regards, Peter Sinkovic

            Peter Sinkovic added a comment - Dear Michael, despite the (unfortunate) statement about not including this feature, let me attach a screenshot of a physical kanban board we are using, so you can see the "real thing". We wanted to start using kanban boards in jira (mostly because tracking time / metrics), but its not really possible when you cant see anything on board (tested on 23" widescreen monitor). Regards, Peter Sinkovic

            Many thanks for reporting this issue, however this is not something we are going to add to JIRA Agile at this time.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Many thanks for reporting this issue, however this is not something we are going to add to JIRA Agile at this time. Regards, JIRA Agile Team

              Unassigned Unassigned
              tribeiro Thiago Ribeiro
              Votes:
              2 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: