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

As a user, I would like the Column Constraint to apply for Quick Filter

XMLWordPrintable

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

      It seems that the Column Constraint does not apply when selecting the quick filter. When 3 stories are in the status In Progress with a maximum of 2 issue counts, it turns red. However, it keeps red even after applying the quick filter which returns zero results for the status In Progress.

      Before quick filter applied:

      After quick filter applies:

      The expectation would be that the red color disappear if the amount of issues/stories appear in the column is not more than max issue counts.

        1. column1.png
          46 kB
          Zul NS [Atlassian]
        2. column2.png
          28 kB
          Zul NS [Atlassian]

            [JSWSERVER-9729] As a user, I would like the Column Constraint to apply for Quick Filter

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3068032 ] New: JAC Suggestion Workflow 3 [ 3661879 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2623464 ] New: JAC Suggestion Workflow [ 3068032 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2324190 ] New: Confluence Workflow - Public Facing v4 [ 2623464 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2041997 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2324190 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2030029 ] New: JIRA PM Feature Request Workflow v2 [ 2041997 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736194 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2030029 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 552856 ] New: JIRA PM Feature Request Workflow v2 [ 736194 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Martin (Inactive) added a comment -

            Copy of my answer on the Answers page:

            Using Quick Filters to avoid WIP or column constraints does not make sense and would essentially bypass them. The column constraint is set for a reason, to denote a minumum or maximum number of issues in a column (which are issues in one or more statuses).

            Martin (Inactive) added a comment - Copy of my answer on the Answers page: Using Quick Filters to avoid WIP or column constraints does not make sense and would essentially bypass them. The column constraint is set for a reason, to denote a minumum or maximum number of issues in a column (which are issues in one or more statuses).

              Unassigned Unassigned
              znoorsazali Zul NS [Atlassian]
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: