View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0025825mantisbtfilterspublic2019-05-31 03:252019-06-13 18:22
Reporterjacekwww Assigned Todregad  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Product Version2.20.0 
Summary0025825: filter goes back atomaticly from „advanced Filters“ to „simple filters“ on click to „ Assigned to Me“ in my_view
Description

The filter returns automatically from "advanced filters" to "simple filters" after clicking "Assigned to me". The result is that in the window "view issues" the fiter is then on Assignet To: Any. The same problem exists with permament link.

Only after switching to "Advanced Filters" the filter "Assigned To" becomes active and only own tickets are displayed.

TagsNo tags attached.
Attached Files
filter_1.png (18,934 bytes)   
filter_1.png (18,934 bytes)   
filter_2.png (34,684 bytes)   
filter_2.png (34,684 bytes)   
filter_3.png (35,096 bytes)   
filter_3.png (35,096 bytes)   

Activities

dregad

dregad

2019-05-31 04:16

developer   ~0062169

@jacekwww Sorry but I'm not able to reproduce the problem you're describing. Clicking on the My View Page boxes' title indeed opens the View Issues page in Simple Filter mode even if it was previously in Advanced mode, but the filter is set as expected (i.e. to my own username for the Assigned to me box).
jacekwww

jacekwww

2019-05-31 04:48

reporter   ~0062171

@dregad

The same thing happens to me when you open the permament link

e.g. https://xxx/search.php?project_id=0&status[]=10&status[]=20&status[]=30&status[]=40&status[]=50&status[]=61&handler_id=3080&sticky=on&sort=last_updated&dir=DESC&hide_status=-2&match_type=0)

You always end up on the page with "simple filters". After switching to the "advanced filter" everything is displayed as desired, unfortunately, when reopening the link, the filter is again in "simple filter".
Maybe it's because the installation is more than 10 years old. The error occurs after the upgrade from 1.2.20 to 2.20.0 (without intermediate steps).
There are already 18639 filters.
dregad

dregad

2019-05-31 05:44

developer   ~0062172

Also not reproducible here...

https://mantisbt.org/bugs/search.php?project_id=0&status[]=10&status[]=20&status[]=30&status[]=40&status[]=50&status[]=61&handler_id=3080&sticky=on&sort=last_updated&dir=DESC&hide_status=-2&match_type=0

Maybe @cproensa can comment further since he authored recent changes to the filter API that may be causing the behavior you're experiencing.
jacekwww

jacekwww

2019-05-31 06:31

reporter   ~0062174

I think I found it: it's up to the loadbalaner. I run mantis behind a loadbalancer (ALB in AWS) with 2 ManitsBT instances (see picture) and a MySQL database. When I shut down an instance, filter works as designed.

Other functions works correctly with two ManitsBT instances.

networkplan.png (11,573 bytes)   
networkplan.png (11,573 bytes)   
dregad

dregad

2019-05-31 07:54

developer   ~0062175

Thanks for the feedback. Not being familiar with how a loadbalancer would interact with the filter API, I'm afraid I can't help you much further.
jacekwww

jacekwww

2019-05-31 08:03

reporter   ~0062176

Thank you for your help.
The source of the error has been located, so I need to change the loadbalancer so that it always connects to a single server (Source IP Persistence).

best regards jacek
dregad

dregad

2019-05-31 08:42

developer   ~0062177

Thanks for the feedback, glad to hear you found the solution to your problem.