MUX Views Inherits Previously Selected View's Filter, Causing Missing or Incomplete Task Rows
search cancel

MUX Views Inherits Previously Selected View's Filter, Causing Missing or Incomplete Task Rows

book

Article ID: 453261

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

In the MUX Tasks tab, a saved view with no filter of its own displays fewer tasks or zero after the user has visited a different saved view that has an Advanced Filter applied, even though the unfiltered view should always show every task. The same behavior is observed on Projects list view as well.

Steps to Reproduce

  1. Create a task-list view with no filters applied (e.g., "View 1") set to Timeline layout.
  2. Create a task-list view with an Advanced Filter applied on a status field (e.g., "View 2") set to Grid layout.
  3. Open the project and navigate to the Tasks tab. Select the unfiltered view ("View 1") and note the initial row count.
  4. Switch to the filtered view ("View 2") and confirm its filter applies as expected.
  5. Switch back to the unfiltered view ("View 1").

Expected Result:

Step 3 displays the original baseline row count, as "View 1" has no filter and should display all data.

Actual Result:

Step 3 displays fewer rows (or zero) because "View 1" silently inherits and applies the filter clause from the previous view.

Workaround:

A full browser page reload (F5) restores the correct result.

Environment

Clarity 16.4.2

Cause

Due to DE210974

Resolution

Engineering is reviewing DE210974