View Issues Filter

[ariehorst]

Hello,

Today I experienced a nasty feature which in my perspective may also qualify as a bug. Whenever you switch projects, the filter settings in the View Issues page get reset to almost completely logical values except for one: the "assigned to" field gets reset to "Me".
I experienced the nasty consequences of this feature when I was first viewing issues of a "Parent Project A" where I changed the setting of the filter to "assigned to any", after which I switched to it's "Sub Project B", moving all issues to "Parent Project A", and then deleted "Sub Project B", not noticing that "assigned to" switched back to "Me".
Now luckily, there was only one issue in there not assigned to me.

Is there a way to let these filters have other default settings? Or should I file a bug report (I will anyway if the answer is anything related to "hack in the code").

Thanks

[atrol]

After switching to a project you will get the last filter you used with this project (and not any predefined defaults)
IMO this works fine for typical workflows but probably not for your use case.

[ariehorst]

If that is supposed to be the behavior than it isn't working over here (on 1.2.4 nor 1.2.10). If I change the filter, switch to another project and switch back again, the filter settings are not restored. I don't know if the behavior you mention should also work over sessions (logout and login again, possibly with a fresh browser), but then it would already have "stabilized" to my preferred settings, as i have changed this setting before at least once for all of the applicable projects.

[atrol]

I am not able to reproduce the behaviour.
Are you able to reproduce the issue with a Mantis2Go (see my signature for it) installation?
If so, can you give step by step instructions?

[ariehorst]

Took a while, but I managed to reproduce it and find the actual problem.
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.

So it seems that the top-level project dictates or overwrites the filter settings for the sub-project. With only two top level projects the behavior is as you said, but not with sub-projects.
Remembering settings on a per project basis is perfectly fine with me. It is intuitive and sensible. But from my perspective this should be kept consistent and top-level projects should not dictate the settings for sub-projects.

[atrol]

So it seems that the top-level project dictates or overwrites the filter settings for the sub-project. With only two top level projects the behavior is as you said, but not with sub-projects.
Remembering settings on a per project basis is perfectly fine with me. It is intuitive and sensible. But from my perspective this should be kept consistent and top-level projects should not dictate the settings for sub-projects.

I agree with this. You should enter a report at http://www.mantisbt.org/bugs
Probably sub-projects are not well designed in some aspects. Have a look at http://www.mantisbt.org/bugs/view.php?id=10658 and the related issues.
http://www.mantisbt.org/bugs/view.php?id=10658