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

Improve documentation for column constraints in JIRA Software (and JIRA Agile)

XMLWordPrintable

    • 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.

      According to the documentation on Configuring Columns - Setting Column Constraints:

      Constraints specify how many issues a column can contain. You can specify constraints for all columns, or just some of them.

      You can choose to exclude sub-tasks from the count. This is useful if you want to constrain the number of major tasks (stories) your team is working on, rather than the total number of individual tasks. This is likely to be more relevant to Scrum teams than to Kanban teams.

      Reading the docs, I believe the column should display only the maximum number set in the column constraint, but it doesn't (tested for both Scrum and Kanban). The only difference will be that column header now had a red line added:

        1. kanban.png
          kanban.png
          159 kB
        2. scrum.png
          scrum.png
          159 kB

            [JSWSERVER-10627] Improve documentation for column constraints in JIRA Software (and JIRA Agile)

            Christopher Hurney added a comment -

            I can see the value in this behavior, however, isn't this minimally useful compared to the (very simple) ability to truncate the number of issues visible in the 'DONE' column alone based on some criteria (i.e. number of issues, dates, etc)

            Christopher Hurney added a comment - I can see the value in this behavior, however, isn't this minimally useful compared to the (very simple) ability to truncate the number of issues visible in the 'DONE' column alone based on some criteria (i.e. number of issues, dates, etc)

            iceman added a comment - - edited

            Hi Clarissa,

            Thank you for your feedback. We've already fixed the documentation, to state the expected behaviour more clearly.

            Please refer to Setting column constraints in the following pages:

            Thanks again!

            Cheers,
            Ashley
            JIRA Software

            iceman added a comment - - edited Hi Clarissa, Thank you for your feedback. We've already fixed the documentation, to state the expected behaviour more clearly. Please refer to Setting column constraints in the following pages: https://confluence.atlassian.com/display/JIRASOFTWARECLOUD/Configuring+Columns https://confluence.atlassian.com/display/AGILE/Configuring+Columns Thanks again! Cheers, Ashley JIRA Software

            Martin (Inactive) added a comment -

            This is not a bug, it is a misunderstanding based on the ambiguous text which we will update in due course.

            The expected behaviour is that all issues in the columns will be shown, but that when the number of issues exceeds the maximum then the colour of the column will turn to red. This is a visual indicator only and acts as a signal for the team to swarm and reduce the items in that column before other work. This is to reduce bottlenecks and to increase throughput of items on the board.
            There is also a minimum constraints, which signals using a yellow column, when the minimum required number of items are not in a column.

            The column constraints feature can optionally include sub-tasks in this count.

            Kind regards,
            Martin
            JIRA Software

            Martin (Inactive) added a comment - This is not a bug, it is a misunderstanding based on the ambiguous text which we will update in due course. The expected behaviour is that all issues in the columns will be shown, but that when the number of issues exceeds the maximum then the colour of the column will turn to red. This is a visual indicator only and acts as a signal for the team to swarm and reduce the items in that column before other work. This is to reduce bottlenecks and to increase throughput of items on the board. There is also a minimum constraints, which signals using a yellow column, when the minimum required number of items are not in a column. The column constraints feature can optionally include sub-tasks in this count. Kind regards, Martin JIRA Software

            Gregory Kneller added a comment -

            My users noticed this in jira v5.2.11 as well

            Gregory Kneller added a comment - My users noticed this in jira v5.2.11 as well

              Unassigned Unassigned
              cgauterio Clarissa Gauterio (Inactive)
              Votes:
              26 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: