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

swimmlane sensitive WIP-limits

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • 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 Kanban teamlead I'd like to specify a work-in-progress limit based
      on swimmlanes to enable the team to handle "prio-1-emergency-ASAP"-tasks
      in a dedicated ASAP swimmlane whitout interfering the current WIP.

      example:

      • board has the standard 3 columns
      • board has 2 swimmlanes: ASAP and OTHER
      • WIP-limit on "in progress" is 3
      • team is working on 3 tasks in OTHER (ASAP is empty)

      now a real urgend issue is opened by support.
      this issue should appear in the ASAP swimmlane and the team
      has to start immediatly.
      The WIP-limit of "in progress" does not allow to start the
      work on a 4th issue...

      Therefore I want to be able to set diffrent WIP-limit for
      diffrent swimmlanes

            [JSWSERVER-5637] swimmlane sensitive WIP-limits

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3067104 ] New: JAC Suggestion Workflow 3 [ 3657994 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2622971 ] New: JAC Suggestion Workflow [ 3067104 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2322661 ] New: Confluence Workflow - Public Facing v4 [ 2622971 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2040527 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2322661 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2033045 ] New: JIRA PM Feature Request Workflow v2 [ 2040527 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 737360 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2033045 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 400793 ] New: JIRA PM Feature Request Workflow v2 [ 737360 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Tom Kotecki (Inactive) made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Nicholas Muldoon [Atlassian] made changes -
            Link New: This issue duplicates GHS-3681 [ GHS-3681 ]

              Unassigned Unassigned
              96dd583194c8 Sascha Ernst
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: