0014158: Top level project dictates filter settings for subprojects

View Issue Details [ Jump to Notes ] [ Wiki ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0014158

mantisbt

filters

public

2012-04-16 08:20

Reporter

ariehorst

Assigned To

Priority

normal

Severity

minor

Reproducibility

always

Status

new

Resolution

open

Platform

x64

Windows

OS Version

Product Version

1.2.10

Target Version

Fixed in Version

Summary

0014158: Top level project dictates filter settings for subprojects

Description

When a construct of a top level project with multiple subprojects is used (independent of the depth), the filter settings are only remembered for the top level project, and not the sub-projects. This will cause the filter settings to change to the settings of the top level project whenever you switch between subprojects, instead of the last used settings of that subproject.

Steps To Reproduce

The steps to reproduce:
Create a Project "ProjectA" with default settings.
Create a Project "SubProjectA" with default settings and add it as sub-project to ProjectA.
Create a project "SubProjectB" with default settings and add it as sub-project to ProjectA.
Switch to the View Issues page and select SubProjectA.
Change "Assigned to" to "Myself" and apply filter.
Switch to SubProjectB and then back to SubProjectA.
The "Assigned to" is now set to "any" and does not restore to "Myself"
Switch to ProjectA.
Change "Assigned to" to "Myself" and apply filter.
switch to SubProjectA.
The "Assigned to" remains to be set to "Myself" and does not restore to "any"
change "assigned to" to any.
switch to SubProjectB and then back to SubProjectA.
"Assigned to" is again set to "Myself" instead of the previously applied filter with "any" for this project.

Issue History
Date Modified	Username	Field	Change
2012-04-16 08:20	ariehorst	New Issue

Relationships

Notes
There are no notes attached to this issue.