Quick filtering a subtask in a board will hide it's parent's status in the swimlane

XMLWordPrintable

    • 8
    • 4
    • Severity 3 - Minor

      Issue Summary

      When selecting a quick filter in an active sprint or kanban backlog board that filters sub-tasks of a ticket that shows up in the swimlane will result in hiding the parent's status label and issue type icon.

      Environment

      Reproducible on Jira 8.0.2
      Not reproducible on Jira 7.7 and 7.13

      Steps to Reproduce

      1. Login with the administrator account
      2. Create a Jira Software scrum or kanban project
      3. Create a story and assign it to User A
      4. Create a sub-task of that story and assign it to User B
      5. Add swimlane to the stories, and add two quick filters - one to look for issues assigned to User A, and another to look for issues assigned to User B
      6. At the active sprint view or kanban backlog, select the first quick filter to User A. The parent ticket will still have it's issue type icon and status label information in the swimlane
      7. Unselect the quick filter, and select the quick filter to look for ticket assigned to User B (assignee of subtask)

      Expected Results

      The parent ticket will persist with the ticket's information of issue type icon and status label.

      Actual Results

      The parent ticket hide the issue type icon and it's status label.

      Screenshots

      Without filters, expected behaviour:

      With quick filter to the assignee of the subtask, hidden information:

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

        1. Expected_behaviour.png
          74 kB
          Felipe Prusch
        2. Hidden_IssueType_and_Status.png
          70 kB
          Felipe Prusch

            Assignee:
            Dmytro Borshchov
            Reporter:
            Felipe Prusch (Inactive)
            Votes:
            5 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: