We've been seeing users project scope settings (include Parent Projects and/or Child Projects) occasionally wiped out without the user making a change to their settings OR clicking a link from someone else with different settings. We encourage our users to keep Child Projects checked so that when sitting in a Release Train or above, they are seeing work in their child teams. If this setting is blanked out without the user being aware of it, they may be making decisions on a view without really having all the data.
For example, an RTE looking at the Portfolio Items page at Features may be seeing only features directly in the Release Train not realizing that features in the child teams exist but are not currently visible, because they rely on that setting to stay in place unless they intentionally change it.
This came up when an RTE was looking at a User Story data quality page - this page only shows user stories with issues that break our data quality rules, so if it shows nothing, it looks like there are no issues, when the truth is that the user's Child Projects setting had dropped out without them intentionally making a change.
We've opened a ticket, but without being able to 'trap' the issue via either video or identifying reproducible steps, we're not getting very far.
Has anyone else seen this recently?
------------------------------
Terry Ginzburg
------------------------------