Ability to hide inactive users on the list and the board

XMLWordPrintable

    • 1

      Issue Summary

      Users are experiencing an issue where old (deactivated) accounts continue to appear in the top bar when grouping by assignee on Kanban boards, even with filters applied that should not include these users.

      Steps to Reproduce

      1. Navigate to a Kanban board within a project.
      2. Apply any filter that groups issues by assignee.
      3. Observe the list of grouped items and note the inclusion of deactivated user accounts without assigned issues under current view/filter settings.

      Expected Results

      When applying filters, especially those related to active tasks/assignees:

      • Deactivated user accounts should be automatically excluded from views/lists if they have no relevant active issues associated with them for the filtered criteria.
      • The UI elements such as groupings and search bars should only display currently active users who meet filtering conditions set forth by end-users.

      Actual Results

      Despite setting appropriate filters that logically imply the exclusion of inactive/decommissioned account holders:

      • Old/deactivated user profiles persistently show up alongside valid entries across various interface components like quick-filters/top-bars/group-by lists etc., leading to unnecessary clutter and confusion.
      • When expanding the group for an inactive user, it shows as empty which confirms that no issues are currently assigned to them under the filtered view.

      Workaround

      Currently, there is no known workaround for preventing deactivated users from appearing on Kanban boards when grouping by the assignee with filters applied. The only available method involves manually unassigning all tasks from inactive accounts; however, this approach is not sustainable long-term due to its repetitive nature each time a user becomes inactive.

            Assignee:
            Unassigned
            Reporter:
            Willian Sousa
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: