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

As a Rapid board user, I would like to see MY restrictions only

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • AgileBoard
    • 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.

      assignee = currentUser()

      or

      assignee = currentUser() or (reviewer = currentUser() AND status in "Review")

      are handy filters for keeping one Team-board but everyone is able to easily restrict his view BUT..

      Restricting of Swimlanes are do not know anything about these filters, so still view is filtered to currentUser with one issue in progess and restriction of max "1" in progress still leads to a red lane ... for everyone ;( That's not so handy ...

      related to but not the same as like
      GHS-3681

            [JSWSERVER-10010] As a Rapid board user, I would like to see MY restrictions only

            Tom Kotecki (Inactive) added a comment -

            Many thanks for reporting this issue. This is working as intended - just because a filter eliminates issues from view doesn't mean the WIP limit shouldn't be enforced; you can easily imagine situations such as filters eliminating bugs which would otherwise suggest WIP limit is not reached while in fact it is.

            Regards

            Tom Kotecki
            Product Manager, JIRA Agile

            Tom Kotecki (Inactive) added a comment - Many thanks for reporting this issue. This is working as intended - just because a filter eliminates issues from view doesn't mean the WIP limit shouldn't be enforced; you can easily imagine situations such as filters eliminating bugs which would otherwise suggest WIP limit is not reached while in fact it is. Regards Tom Kotecki Product Manager, JIRA Agile

              Unassigned Unassigned
              c34ad611bdfc childnode
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: