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

As a project manager I would like to spread one Kanban WIP limit across multiple subcolumns

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 6
    • 4
    • Hide
      Atlassian Status as at 07 December 2015

      Thanks for your feedback and comments, the JIRA team is working hard to improve the product and we are aware of the many requests here on jira.atlassian.com

      We understand that this is a significant issue for many of you, however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.

      Kind regards,
      Martin
      JIRA Software

      Show
      Atlassian Status as at 07 December 2015 Thanks for your feedback and comments, the JIRA team is working hard to improve the product and we are aware of the many requests here on jira.atlassian.com We understand that this is a significant issue for many of you, however we cannot provide any guidance at this time as to when, or if, we'll be implementing it. Kind regards, Martin JIRA Software
    • 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.

      1. agile_project_management_with_kanban.jpg
        agile_project_management_with_kanban.jpg
        232 kB
      2. image-2018-01-09-02-02-33-365.png
        image-2018-01-09-02-02-33-365.png
        28 kB
      3. KanbanAndScrumInfoQVersionFINAL.pdf (page 59 of 122).jpg
        KanbanAndScrumInfoQVersionFINAL.pdf (page 59 of 122).jpg
        9 kB
      4. kanban-kick-start-example.jpg
        kanban-kick-start-example.jpg
        232 kB
      5. rtp_card_color.png
        rtp_card_color.png
        49 kB
      6. rtp_field-png.png
        rtp_field-png.png
        13 kB

          [JSWSERVER-2521] As a project manager I would like to spread one Kanban WIP limit across multiple subcolumns

          Nicolo' Manzotti added a comment - Possible duplicate spotted: https://jira.atlassian.com/browse/JRASERVER-71911

          Azure Boards has this feature: [Manage columns on your board - Azure Boards | Microsoft Learn|https://learn.microsoft.com/en-us/azure/devops/boards/boards/add-columns?view=azure-devops]

          It would be greatly beneficial for teams utilising Kanban to be able to segment columns and focus more on flow.

          joshua.challenor added a comment - Azure Boards has this feature: [Manage columns on your board - Azure Boards | Microsoft Learn|https://learn.microsoft.com/en-us/azure/devops/boards/boards/add-columns?view=azure-devops] It would be greatly beneficial for teams utilising Kanban to be able to segment columns and focus more on flow.

          It was really surprising that Jira doesn't let us to set a single WIP limit on a kanban board. When I've read about it, that seems to be how most people does kanban. And this ticket having been here for 14 years... Wow, can't really expect much to happen.

          This was the first issue I've looked at in the Jira backlog, hope I never find anything really critical that we need, I won't expect it to be corrected.

          Johan Serebrink added a comment - It was really surprising that Jira doesn't let us to set a single WIP limit on a kanban board. When I've read about it, that seems to be how most people does kanban. And this ticket having been here for 14 years... Wow, can't really expect much to happen. This was the first issue I've looked at in the Jira backlog, hope I never find anything really critical that we need, I won't expect it to be corrected.

          Ryan added a comment -

          +1 - without this feature - makes it near impossible to fully implement KanBan (as explained by Eric Brechner).

          Ryan added a comment - +1 - without this feature - makes it near impossible to fully implement KanBan (as explained by Eric Brechner).

          Zoran Vujkov added a comment - - edited

          As a tool that promote Kanban template, you should certainly support Kanban practice WIP limit for multiple columns and PULL mechanism. 

          And user is not PM, user here is a Kanban team

          Zoran Vujkov added a comment - - edited As a tool that promote Kanban template, you should certainly support Kanban practice WIP limit for multiple columns and PULL mechanism.  And user is not PM, user here is a Kanban team

          I opened a corresponding ticket for the Cloud version of Jira: JRACLOUD-77822

          thomas.heller added a comment - I opened a corresponding ticket for the Cloud version of Jira: JRACLOUD-77822

          Another vote, this is a very important distinction to be able to make in an actual Kanban board

          keith kennedy added a comment - Another vote, this is a very important distinction to be able to make in an actual Kanban board

          Vincent added a comment -

          It would also be great to have a new Jira's status... almost 5 years later! 

          Vincent added a comment - It would also be great to have a new Jira's status... almost 5 years later! 

          Vincent added a comment -

          It's really hard to implement the pull approach when there is no done sub-column to clearly show a task is waiting. So without this feature I can't tell my teams that Jira supports Kanban, it's more a todo list feature Trello-like. Super frustrated to have to use and pay for other tools. Please just implement such a feature that will help all teams to better practice lean. 

          Vincent added a comment - It's really hard to implement the pull approach when there is no done sub-column to clearly show a task is waiting. So without this feature I can't tell my teams that Jira supports Kanban, it's more a todo list feature Trello-like. Super frustrated to have to use and pay for other tools. Please just implement such a feature that will help all teams to better practice lean. 

          David Wilson added a comment - - edited

          Hey to all who are watching this issue. Just FYI, I've been reaching out to friends and colleagues, agile coaches, teams we coach, etc, to vote this item up. I challenge all of you to do the same. Provide a VERY simple instruction to create an account, and to vote. Tell them it takes no more than 2 minutes.  Simple! How many votes can we get? It seems like getting to 400 is a milestone...can we get there? Higher? This item has been on the backlog for far too long!

          David Wilson added a comment - - edited Hey to all who are watching this issue. Just FYI, I've been reaching out to friends and colleagues, agile coaches, teams we coach, etc, to vote this item up. I challenge all of you to do the same. Provide a VERY simple instruction to create an account, and to vote. Tell them it takes no more than 2 minutes.  Simple! How many votes can we get? It seems like getting to 400 is a milestone...can we get there? Higher? This item has been on the backlog for far too long!

          It is really difficult to make a serious kanban board with Jira without this feature. 

          Rafael Caceres added a comment - It is really difficult to make a serious kanban board with Jira without this feature. 

          For additional reference and an example of the type of functionality, this would be simliar to the "Kanban Combined WIP for Jira." While I love the work that MrAddOn has done with this, it's really a feature that should be available for any Jira instance supporting Kanban.

          Atlassian - when filtering by label "kanban" this is one of the top two items listed both for server and for cloud. Please consider moving this into consideration!

          David Wilson added a comment - For additional reference and an example of the type of functionality, this would be simliar to the " Kanban Combined WIP for Jira ." While I love the work that MrAddOn has done with this, it's really a feature that should be available for any Jira instance supporting Kanban. Atlassian - when filtering by label "kanban" this is one of the top two items listed both for server and for cloud. Please consider moving this into consideration!

          I'm surprised that Jira doesn't have this!

          Dak Washbrook added a comment - I'm surprised that Jira doesn't have this!

          david.l.wilson2 added a comment - - edited

          This would be a huge benefit to Kanban. One column can carry two statuses today, but having this option would make the visualization of the board much easier to interpret (which is the first core practice of Kanban). I might recommend this is need for the team, and not a project manager as the title states.

          One point to emphasize that is implied through the images - the WIP limit would apply to the parent column. This means if I have a parent TEST column, and had sub columns of READY TO TEST and TESTING, the sum of the sub columns would be applied against the min/max limits on the TEST column.

          I added my vote...hope we can pick up steam with this one.

          david.l.wilson2 added a comment - - edited This would be a huge benefit to Kanban. One column can carry two statuses today, but having this option would make the visualization of the board much easier to interpret (which is the first core practice of Kanban). I might recommend this is need for the team, and not a project manager as the title states. One point to emphasize that is implied through the images - the WIP limit would apply to the parent column. This means if I have a parent TEST column, and had sub columns of READY TO TEST and TESTING, the sum of the sub columns would be applied against the min/max limits on the TEST column. I added my vote...hope we can pick up steam with this one.

          +1

          Bryan Nance added a comment - +1

          starmero added a comment -

          Please implement this - there is a workaround by having multiple statuses in a single column, but it's unwieldy and leads to a less intuitive board.

          Good Kanban practise requires this to be available

          An Update on this would be appreciated - the last one was in 2015...

          starmero added a comment - Please implement this - there is a workaround by having multiple statuses in a single column, but it's unwieldy and leads to a less intuitive board. Good Kanban practise requires this to be available An Update on this would be appreciated - the last one was in 2015...

          Created: 07/Oct/2010
          Oh my lord. Guess we'll never see this feature.

          Kasper Skov added a comment - Created: 07/Oct/2010 Oh my lord. Guess we'll never see this feature.

          JoAMoS added a comment -

          +1 Yes Please! 

          JoAMoS added a comment - +1 Yes Please! 

          +100 :- )

          Hans Riethmann added a comment - +100 :- )

          Gerhard added a comment -

          +1

          Gerhard added a comment - +1

          Please implement this.

          Josh Costella added a comment - Please implement this.

          This would be an amazing thing for us. Lots of our teams are struggling with the same thing, and we definitely dont want them to maintain digital boards and physical only to track sub statuses.

          Karanpreet Kaur added a comment - This would be an amazing thing for us. Lots of our teams are struggling with the same thing, and we definitely dont want them to maintain digital boards and physical only to track sub statuses.

          sm-g610f

          Kanjana Kraidam added a comment - sm-g610f

          Bret Mogilefsky - QEABA added a comment - - edited

          I liked this solution involving placing multiple statuses in the same column for the fact that it puts a single WIP limit over multiple "sub-columns" and seems "in-keeping" with existing features in the board. I don't like putting the state name on the card when we just want to see a simple "Done/Ready for Pull" flag; it adds visual noise to every card which detracts from the value of doing this.

          I think I have an alternative that achieves the same result but is more subtle... You can change card colors based on status. You can use this to show when cards in a given column are "Done/Ready for Pull" state without adding a separate column or swimlane or noise on all your cards:

          • Add a second "...Done" status representing each sub-column where you Wish you had it.
            • So for example, if the column was "Grooming", you would add "GroomingDone".
          • Put both statuses under the same column in the board configuration.
            • Configure your board
            • Select "Columns" at left
            • Map the "Done" statuses (statii? 🤔) under their corresponding columns
          • Referencing the post above, change the card color to something agreed upon that isn't already used for other purposes (eg green) when the status is in any of the "...Done" ones.
            • Select "Card colors" at left
            • Select "Queries" under "Colors based on"
            • Pick the desired color from color picker
            • List your done status in JQL, eg "status in (GroomingDone, DevelopDone)"
            • "Add" configuration

          This works pretty well... When you drag from into the next column, a drop-zone appears for each status in that column. When you drop the card in a Done status zone, the color is set. When you drop the card in a not-Done status zone, the color is cleared.

          The only problem here is that as @flaimo mentions, the status drop-zones don't appear unless you're dragging between columns, so you have to drag a card back a column, then forward just to have an opportunity to drop it in the Done state. This does result in unnecessary status changes which you might not be able to stomach if you have triggers or reports that these extraneous status changes pollute.

          However, there's another quick way to do the status transition without an extraneous drag-drop-to-another-column step between:

          • Hover over the card
          • Hit "." to bring up the dialog
          • Type "Done" to filter to the statuses you're looking for
          • Arrow down to select the right status
            • If you limit the valid workflow transitions, you won't have to do this
          • Hit Enter

          In my opinion being unable to drag to another status in the same column is just a bug for Atlassian to fix, but that's probably easier for them to do than add some baroque sub-column layout capability. Maybe it's worth piling into that discussion?

          [Edit: Added a screenshot]

          Bret Mogilefsky - QEABA added a comment - - edited I liked this solution involving placing multiple statuses in the same column for the fact that it puts a single WIP limit over multiple "sub-columns" and seems "in-keeping" with existing features in the board. I don't like putting the state name on the card when we just want to see a simple "Done/Ready for Pull" flag; it adds visual noise to every card which detracts from the value of doing this. I think I have an alternative that achieves the same result but is more subtle... You can change card colors based on status. You can use this to show when cards in a given column are "Done/Ready for Pull" state without adding a separate column or swimlane or noise on all your cards: Add a second "...Done" status representing each sub-column where you Wish you had it. So for example, if the column was "Grooming", you would add "GroomingDone". Put both statuses under the same column in the board configuration. Configure your board Select "Columns" at left Map the "Done" statuses (statii? 🤔) under their corresponding columns Referencing the post above, change the card color to something agreed upon that isn't already used for other purposes (eg green) when the status is in any of the "...Done" ones. Select "Card colors" at left Select "Queries" under "Colors based on" Pick the desired color from color picker List your done status in JQL, eg "status in (GroomingDone, DevelopDone)" "Add" configuration This works pretty well... When you drag from into the next column, a drop-zone appears for each status in that column. When you drop the card in a Done status zone, the color is set. When you drop the card in a not-Done status zone, the color is cleared. The only problem here is that as @flaimo mentions , the status drop-zones don't appear unless you're dragging between columns, so you have to drag a card back a column, then forward just to have an opportunity to drop it in the Done state. This does result in unnecessary status changes which you might not be able to stomach if you have triggers or reports that these extraneous status changes pollute. However, there's another quick way to do the status transition without an extraneous drag-drop-to-another-column step between: Hover over the card Hit "." to bring up the dialog Type "Done" to filter to the statuses you're looking for Arrow down to select the right status If you limit the valid workflow transitions, you won't have to do this Hit Enter In my opinion being unable to drag to another status in the same column is just a bug for Atlassian to fix , but that's probably easier for them to do than add some baroque sub-column layout capability. Maybe it's worth piling into that discussion? [Edit: Added a screenshot]

          Adding my vote for this too. The literature and experience in the field is clear - multi-column WIP limits Doing | Done really works. It would be great if JIRA supported this concept with sub-columns out of the box.

          Kanban Combined WIP for JIRA is a good plugin, but the feature seems valuable enough to add to the base product (just like Kanban Backlogs was obviously a needed addition).

          Thanks for continuing to collect feedback from the practitioners, we know you read them!

          Jason Golden added a comment - Adding my vote for this too. The literature and experience in the field is clear - multi-column WIP limits Doing | Done really works. It would be great if JIRA supported this concept with sub-columns out of the box. Kanban Combined WIP for JIRA is a good plugin, but the feature seems valuable enough to add to the base product (just like Kanban Backlogs was obviously a needed addition). Thanks for continuing to collect feedback from the practitioners, we know you read them!

          Hi Everyone,

          I just created a workaround for it with JIRA Workflow Toolbox (https://marketplace.atlassian.com/plugins/com.fca.jira.plugins.workflowToolbox.workflow-toolbox/server/overview). The solution was based on Transition Validators. The validator was the following: Validation based on JQL query. The query was the following:

          assignee = "%{00020}" AND issuetype = "Task" AND status = "In Progress"

          This query returns the number of the tasks of the current user for the next transition, and you can deny the transition if it is breaching the allowed number of tasks. You have to add the specific validator for each transition.

          It's working

          csaba.sari@shore.com added a comment - Hi Everyone, I just created a workaround for it with JIRA Workflow Toolbox ( https://marketplace.atlassian.com/plugins/com.fca.jira.plugins.workflowToolbox.workflow-toolbox/server/overview ). The solution was based on Transition Validators. The validator was the following: Validation based on JQL query . The query was the following: assignee = "%{00020}" AND issuetype = "Task" AND status = "In Progress" This query returns the number of the tasks of the current user for the next transition, and you can deny the transition if it is breaching the allowed number of tasks. You have to add the specific validator for each transition. It's working

          James Tate added a comment -

          @mjopson Any chance we could have this plugin added to the cloud version of Jira? Or adopted by Atlassian / Integrated natively.

          https://marketplace.atlassian.com/plugins/com.rauliki.kanbancombinedWIP.KanbanCombinedWIP/server/overview

          James Tate added a comment - @mjopson Any chance we could have this plugin added to the cloud version of Jira? Or adopted by Atlassian / Integrated natively. https://marketplace.atlassian.com/plugins/com.rauliki.kanbancombinedWIP.KanbanCombinedWIP/server/overview

          flaimo added a comment - - edited

          One follow up to my previous comment. "Doing" and "Done" are often not enough for one column. There could be multiple sub states. This is also described in Agile Project Management with Kanban

          @Martin Jopson: Please keep this aspect in mind when you start implementing features in that direction.

          I still wouldn't solve that with dedicated status values, since they are always called "Doing" and "Done". It would be cumbersome to have JIRA status values like "Implementation Doing", "Implementation Track", "Implementation Done",...

          flaimo added a comment - - edited One follow up to my previous comment. "Doing" and "Done" are often not enough for one column. There could be multiple sub states. This is also described in Agile Project Management with Kanban @Martin Jopson: Please keep this aspect in mind when you start implementing features in that direction. I still wouldn't solve that with dedicated status values, since they are always called "Doing" and "Done". It would be cumbersome to have JIRA status values like "Implementation Doing", "Implementation Track", "Implementation Done",...

          Ray Cooke added a comment -

          Thanks @Annemarie Harzl. Looks like I've got a few options to try now!

          Ray Cooke added a comment - Thanks @Annemarie Harzl. Looks like I've got a few options to try now!

          Ray Cooke added a comment -

          That's a great idea and an obvious solution I didn't think of. Thanks very much @flaimo!

          Ray Cooke added a comment - That's a great idea and an obvious solution I didn't think of. Thanks very much @flaimo!

          flaimo added a comment - - edited

          Our workaround looks like this: I have created a custom field which defines, if a card can be pulled into the next (or previous) column.

          If a card is pulled into another column, the flag is cleared by a post function. Based on the value I display a custom card color.

          Our users aren't quite happy with this, since they have to open the edit dialog to change the flag.
          The version with two states in one column isn't any better, since Drag&Drop doexn't work within a column.

          Instead of a generic limit across columns, I'd rather like to see the Doing/Done concept implemented on an issue level, without the need of multiple status values.

          flaimo added a comment - - edited Our workaround looks like this: I have created a custom field which defines, if a card can be pulled into the next (or previous) column. If a card is pulled into another column, the flag is cleared by a post function. Based on the value I display a custom card color. Our users aren't quite happy with this, since they have to open the edit dialog to change the flag. The version with two states in one column isn't any better, since Drag&Drop doexn't work within a column. Instead of a generic limit across columns, I'd rather like to see the Doing/Done concept implemented on an issue level, without the need of multiple status values.

          @Ray Cooke:

          Hi Ray,
          As far as I understand it you use labels to create sub-states, that are not in the workflow.

          But it is possible to create real sub-states, which are in the workflow (at least for the server version, I don't know if this is true for the Cloud version).
          What do you have to do, to be able to share WIPs and have real sub-states (server version):

          • create two states in the workflow
          • put the two states in the same column (board configuration)
          • display the status of the card on the card (card layout in board configuration)

          Voila, you can share a common WIP, because this is set for the whole column and still have two distinct states, which you can use for reporting.
          It is not as neat as having sub columns, but it works fine and with the status displayed on the card you can easily see which cards are done and which aren't.

          Annemarie Harzl added a comment - @Ray Cooke: Hi Ray, As far as I understand it you use labels to create sub-states, that are not in the workflow. But it is possible to create real sub-states, which are in the workflow (at least for the server version, I don't know if this is true for the Cloud version). What do you have to do, to be able to share WIPs and have real sub-states (server version): create two states in the workflow put the two states in the same column (board configuration) display the status of the card on the card (card layout in board configuration) Voila, you can share a common WIP, because this is set for the whole column and still have two distinct states, which you can use for reporting. It is not as neat as having sub columns, but it works fine and with the status displayed on the card you can easily see which cards are done and which aren't.

          Ray Cooke added a comment -

          Despite @Peter Kerschbaumer's comment being unnecessarily antagonistic, it is true that without the ability to have WIP limits apply across multiple columns, it's a lot harder to set up a board that allows us to use WIP limits appropriately.

          It is I believe possible though. The only way I've found to implement Kanban as a methodology, without having to resort to custom scripts which I don't believe you can do on the Cloud version anyway (happy to be corrected here though if I'm wrong), is by faking "doing / done" sub-states with labels. This is semi-workable because the team can then create custom filters on the board to see what work has finished in its current state and is ready to be pulled. It is a pain though because it's an additional workflow step requiring unexpected changes and it's obviously not actually part of the workflow in JIRA so you're missing reporting advantages. Hopefully this works for you in the interim Peter.

          Life would be a lot easier if this feature were implemented though, so +1 vote from me. Thanks for the hard work on the product @Martin Jopson and the JIRA Software team!

          Ray Cooke added a comment - Despite @Peter Kerschbaumer's comment being unnecessarily antagonistic, it is true that without the ability to have WIP limits apply across multiple columns, it's a lot harder to set up a board that allows us to use WIP limits appropriately. It is I believe possible though. The only way I've found to implement Kanban as a methodology, without having to resort to custom scripts which I don't believe you can do on the Cloud version anyway (happy to be corrected here though if I'm wrong), is by faking "doing / done" sub-states with labels. This is semi-workable because the team can then create custom filters on the board to see what work has finished in its current state and is ready to be pulled. It is a pain though because it's an additional workflow step requiring unexpected changes and it's obviously not actually part of the workflow in JIRA so you're missing reporting advantages. Hopefully this works for you in the interim Peter. Life would be a lot easier if this feature were implemented though, so +1 vote from me. Thanks for the hard work on the product @Martin Jopson and the JIRA Software team!

          peter.kerschbaumer commented "@Martin Jopson, your answer just shows that you either don't understand the simplest mechanics of Lean/Kanban or you just don't care about your customers. Make your pick, none of them is a good choice from your point of view. If you want to sell Jira Agile as a basic Kanban tool, you have to fulfill the basic requirements. Don't lie to your customers."

          We see this request as a valid Suggestion, however we cannot provide any guidance at this time as to when we'll be implementing it. If you would like to know more about how we use JAC then please read more at https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

          Implying I do not care about Atlassian customers and accusing me of lying is unwarranted and unfair.

          Kind regards,
          Martin
          JIRA Software

          Martin (Inactive) added a comment - peter.kerschbaumer commented "@Martin Jopson, your answer just shows that you either don't understand the simplest mechanics of Lean/Kanban or you just don't care about your customers. Make your pick, none of them is a good choice from your point of view. If you want to sell Jira Agile as a basic Kanban tool, you have to fulfill the basic requirements. Don't lie to your customers." We see this request as a valid Suggestion, however we cannot provide any guidance at this time as to when we'll be implementing it. If you would like to know more about how we use JAC then please read more at https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com Implying I do not care about Atlassian customers and accusing me of lying is unwarranted and unfair. Kind regards, Martin JIRA Software

          Without proper WIP-limits implemented Jira Agile is nothing more than a todo-list on steroids, in other words completely worthless for any lean/agile implementation.

          In detail, it will not support Little's Law and theory of constraints which are cornerstones.

          @Martin Jopson, your answer just shows that you either don't understand the simplest mechanics of Lean/Kanban or you just don't care about your customers. Make your pick, none of them is a good choice from your point of view. If you want to sell Jira Agile as a basic Kanban tool, you have to fulfill the basic requirements. Don't lie to your customers.

          Peter Kerschbaumer added a comment - Without proper WIP-limits implemented Jira Agile is nothing more than a todo-list on steroids, in other words completely worthless for any lean/agile implementation. In detail, it will not support Little's Law and theory of constraints which are cornerstones. @Martin Jopson, your answer just shows that you either don't understand the simplest mechanics of Lean/Kanban or you just don't care about your customers. Make your pick, none of them is a good choice from your point of view. If you want to sell Jira Agile as a basic Kanban tool, you have to fulfill the basic requirements. Don't lie to your customers.

          TFS / VSO is catching up with you guys. I've been keeping an eye on all these new goodies coming out, and their pace is pretty rapid:

          http://blogs.msdn.com/b/visualstudioalm/archive/2015/01/21/agile-project-management-futures.aspx

          In particular:
          DoD per column
          Split columns: Doing & Done
          Drag & Drop to swimlanes

          Marius George added a comment - TFS / VSO is catching up with you guys. I've been keeping an eye on all these new goodies coming out, and their pace is pretty rapid: http://blogs.msdn.com/b/visualstudioalm/archive/2015/01/21/agile-project-management-futures.aspx In particular: DoD per column Split columns: Doing & Done Drag & Drop to swimlanes

          Thank you for following, voting and commenting on this issue.
          Unfortunately the comment previously given regarding expectation of delivery is inaccurate.

          We do see it as a valid Suggestion however we cannot provide any guidance at this time as to when we'll be implementing it.

          Regards,
          Martin
          JIRA Agile

          Martin (Inactive) added a comment - Thank you for following, voting and commenting on this issue. Unfortunately the comment previously given regarding expectation of delivery is inaccurate. We do see it as a valid Suggestion however we cannot provide any guidance at this time as to when we'll be implementing it. Regards, Martin JIRA Agile

          > Please can you let us know when this feature will be available.

          Probably not anytime soon. This issue is in Open state, which in JIRA term means not prioritized, and in Atlasssian terms that means it is at best years away. Usually Atlasssian are quite good at closing issues they don't intend to work on anytime soon, but maybe that is just how the JIRA team does it.

          If you need this feature now, then perhaps look to alternatives. There are a couple services built on top of Github issues, which makes a lot of sense if you use GitHub and don't want to many tools for your development. They are very simple and don't support strict workflows, but from agile perspective soft workflows is maybe better as it allows you to be... agile Missing piece going this approach is find a good tool/service to deal with cross project, cross dev team roadmap planning, and for that you might want to have a look at "impact mapping" and if there is any tools/services cable of that.

          André R. added a comment - > Please can you let us know when this feature will be available. Probably not anytime soon. This issue is in Open state, which in JIRA term means not prioritized, and in Atlasssian terms that means it is at best years away. Usually Atlasssian are quite good at closing issues they don't intend to work on anytime soon, but maybe that is just how the JIRA team does it. If you need this feature now, then perhaps look to alternatives. There are a couple services built on top of Github issues, which makes a lot of sense if you use GitHub and don't want to many tools for your development. They are very simple and don't support strict workflows, but from agile perspective soft workflows is maybe better as it allows you to be... agile Missing piece going this approach is find a good tool/service to deal with cross project, cross dev team roadmap planning, and for that you might want to have a look at "impact mapping" and if there is any tools/services cable of that.

          Please can you let us know when this feature will be available.

          Wendy vd Spuy added a comment - Please can you let us know when this feature will be available.

          The split-WIP-column (in-progress and done) as described by Anderson and others is very, very helpful when regulating work across the kanban board. The workarounds at http://thinkinginsoftware.blogspot.com/2014/01/kanban-wip-limit-how-to.html don't cover it. This feature is still necessary for Jira-Agile to properly claim support for kanban.

          Peter Tattersfield added a comment - The split-WIP-column (in-progress and done) as described by Anderson and others is very, very helpful when regulating work across the kanban board. The workarounds at http://thinkinginsoftware.blogspot.com/2014/01/kanban-wip-limit-how-to.html don't cover it. This feature is still necessary for Jira-Agile to properly claim support for kanban.

          Since I voted and started watching this issue our Kanban implementation matured and I came to the conclusion that we could handle this challenge in a better way.

          Basically column WIP limits are necessary for queues and buffers which do not have subcolumns.

          On the other side if there are personal WIP limits imposed by culture then this feature is not necessary. In fact having it will be not realistic. In a team people go on vacation for example so the limits for non buffer/queues will need to be constantly adjusted. If on the contrary everybody has a WIP limit of 1/2 standard issues and 1 urgent/fixed delivery date issue the system works perfectly without the need to explicitely putting a limit at column level. This pragmatic approach has been tested and used by our team for over 2 years with excellent results. I posted about this in http://thinkinginsoftware.blogspot.com/2014/01/kanban-wip-limit-how-to.html

          Nestor Urquiza added a comment - Since I voted and started watching this issue our Kanban implementation matured and I came to the conclusion that we could handle this challenge in a better way. Basically column WIP limits are necessary for queues and buffers which do not have subcolumns. On the other side if there are personal WIP limits imposed by culture then this feature is not necessary. In fact having it will be not realistic. In a team people go on vacation for example so the limits for non buffer/queues will need to be constantly adjusted. If on the contrary everybody has a WIP limit of 1/2 standard issues and 1 urgent/fixed delivery date issue the system works perfectly without the need to explicitely putting a limit at column level. This pragmatic approach has been tested and used by our team for over 2 years with excellent results. I posted about this in http://thinkinginsoftware.blogspot.com/2014/01/kanban-wip-limit-how-to.html

          Jim Skufca added a comment -

          Do you have some guidance on when this might be available? I am looking at alternatives and an ETA would really help my analysis.

          Jim Skufca added a comment - Do you have some guidance on when this might be available? I am looking at alternatives and an ETA would really help my analysis.

          I'm also wondering about the ETA for that one, any news?

          Bastien Rocheron added a comment - I'm also wondering about the ETA for that one, any news?

          I see a comment from 2013 that says this feature will be released within 1 year. Do you still estimate you will deliver this around Oct 2014? Our team has been waiting for this feature and we look forward to when it will be ready.

          Lisa Siegel added a comment - I see a comment from 2013 that says this feature will be released within 1 year. Do you still estimate you will deliver this around Oct 2014? Our team has been waiting for this feature and we look forward to when it will be ready.

          So glad that this will be delivered in the next 6 months! Implementing a true pull system is horrible without this feature.

          stevebargelt added a comment - So glad that this will be delivered in the next 6 months! Implementing a true pull system is horrible without this feature.

          Thanks, I voted for GHS-3561 now.

          Thorbjørn Sigberg added a comment - Thanks, I voted for GHS-3561 now.

          Thorbjorn,

          See https://jira.atlassian.com/browse/GHS-3561 and vote for it if you want to see WIP limits on swim lanes.

          I'm currently looking at Kanbanize which integrates with JIRA solely because it has WIP limits on swim lanes, workflow sub columns that I can set the WIP limit on the parent column, and a UI that is more conducive to workflows with many steps (we have 10 steps). But I would much rather just use JIRA and JIRA Agile.

          Michael DeCourcey added a comment - Thorbjorn, See https://jira.atlassian.com/browse/GHS-3561 and vote for it if you want to see WIP limits on swim lanes. I'm currently looking at Kanbanize which integrates with JIRA solely because it has WIP limits on swim lanes, workflow sub columns that I can set the WIP limit on the parent column, and a UI that is more conducive to workflows with many steps (we have 10 steps). But I would much rather just use JIRA and JIRA Agile.

          Would you consider adding the capability of setting a WIP limit on swimlanes as well?

          Thorbjørn Sigberg added a comment - Would you consider adding the capability of setting a WIP limit on swimlanes as well?

          Great News!

          Ivaylo Stanev added a comment - Great News!

          Great news! I am attaching Henrik Knibergs Kanban Kickstart example, that exemplifies the principle. It is described in detail in Henrik Kniberg book http://www.infoq.com/minibooks/kanban-scrum-minibook and David J Anderson book "Kanban" http://www.djaa.com/kanban-successful-evolutionary-change-your-technology-business-0 Let us know if you need more input on this.

          Haakon Stillingen added a comment - Great news! I am attaching Henrik Knibergs Kanban Kickstart example, that exemplifies the principle. It is described in detail in Henrik Kniberg book http://www.infoq.com/minibooks/kanban-scrum-minibook and David J Anderson book "Kanban" http://www.djaa.com/kanban-successful-evolutionary-change-your-technology-business-0 Let us know if you need more input on this.

          Many thanks for your feedback and votes on this issue. We see this as a valid feature request, and we plan on delivering it to you within the next 12 months.

          Thanks for your patience and we hope you appreciate our open approach to feature requests.

          Regards,
          Tom Kotecki
          Product Manager, JIRA Agile

          Tom Kotecki (Inactive) added a comment - Many thanks for your feedback and votes on this issue. We see this as a valid feature request, and we plan on delivering it to you within the next 12 months. Thanks for your patience and we hope you appreciate our open approach to feature requests. Regards, Tom Kotecki Product Manager, JIRA Agile

          I am waiting too!!

          Roger Oberg added a comment - I am waiting too!!

          Lenny added a comment -

          We are waiting on this feature!

          Lenny added a comment - We are waiting on this feature!

            Unassigned Unassigned
            pleschev Peter Leschev
            Votes:
            385 Vote for this issue
            Watchers:
            158 Start watching this issue

              Created:
              Updated: