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

      I can currently set a WIP limit on a column. When a user violates this, the column tells them this, and allows them to continue to place items into the column. I would like to have the ability to prevent the issue from being transitioned into the column until there is enough space in the WIP limit to handle this issue.

            [JSWSERVER-11032] As a scrum master, I would like to enforce WIP limits

            I totally agree - this is a must have feature for truly using Jira to support Kanban workflows. 

            Jen Christian added a comment - I totally agree - this is a must have feature for truly using Jira to support Kanban workflows. 

            I agree with the other comments, not enforcing WIP limits defeats the point of having a Kanban solution in the first place (Kanbanize for example does this). Moreover, one common option for moving a task between columns in JIRA is to load the task's page and press the status change buttons; from that place the red columns are not even visibile so the user is not aware that he is breaking a WIP limit.

            Giorgio Sironi added a comment - I agree with the other comments, not enforcing WIP limits defeats the point of having a Kanban solution in the first place (Kanbanize for example does this). Moreover, one common option for moving a task between columns in JIRA is to load the task's page and press the status change buttons; from that place the red columns are not even visibile so the user is not aware that he is breaking a WIP limit.

            MaeveC added a comment -

            I would also like to have this added.
            It would be very helpful to our team to ensure fluidity.
            Please re-consider.
            Thanks!

            MaeveC added a comment - I would also like to have this added. It would be very helpful to our team to ensure fluidity. Please re-consider. Thanks!

            flaimo added a comment -

            I second that. Seems like the PO and Dev Team should read a book about kanban again to refresh their knowledge.

            flaimo added a comment - I second that. Seems like the PO and Dev Team should read a book about kanban again to refresh their knowledge.

            This is something that is essential for Kanban in JIRA. Please reconsider this development. I understand the complexities of having an issue on multiple boards and having to check WIP across all boards but it would still be a great tool. JIRA Agile is clearly weighted towards Scrum so a re-balance for the Kanban community would be welcome.

            Alistair Roylance added a comment - This is something that is essential for Kanban in JIRA. Please reconsider this development. I understand the complexities of having an issue on multiple boards and having to check WIP across all boards but it would still be a great tool. JIRA Agile is clearly weighted towards Scrum so a re-balance for the Kanban community would be welcome.

            Many thanks for reporting this issue, however this is not something we plan to add to JIRA Agile at this time.
            Regards,
            JIRA Agile team

            Martin (Inactive) added a comment - Many thanks for reporting this issue, however this is not something we plan to add to JIRA Agile at this time. Regards, JIRA Agile team

              Unassigned Unassigned
              bberenberg Boris Berenberg (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: