View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0026761 | mantisbt | filters | public | 2020-03-04 09:03 | 2022-01-16 05:45 |
Reporter | sadovsf | Assigned To | atrol | ||
Priority | high | Severity | major | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Product Version | 2.23.0 | ||||
Summary | 0026761: Relationship filtering not working properly for none case | ||||
Description | I need to filter all "root" tasks for specific target version. This should be quite simple filter:
This works but only as long as no child task have target version set to | ||||
Steps To Reproduce |
Wanted state: | ||||
Additional Information | Attached files are:
| ||||
Tags | No tags attached. | ||||
Attached Files | |||||
No time to check myself at the moment, but this might be already fixed in next version 2.24.0, see 0026621 |
|
@sadovsf I am curious about the dark background shown on the snapshot, how did you end up with a dark theme? |
|
Iam actually working on quite a big client side application for planning and project overview. Part of it being own fast php api for mass operations in mantis and part typescript api for client side of things. Results are ability to download thousands tasks from dB into client side app and work with it locally with indo redo support and stuff. Then you hit save and everything gets. Stored in mantis. Part of this was request from our employees to have dark theme so I did reskin of whole mantis and add button to switch themes into mantis toolbar using simple js code. Thanks to this we now have slightly better looking light and dark themes that works everywhere. It's not yet finished but if you would like to I could probably share CSS along with js that handles switching in forum of simple plugin maybe � |
|
sadovsf, I tried latest version and was not able to reproduce using the given information. Feel free to reopen the issue at a later time if you should still encounter the problem after upgrading. |
|
I have to say that even on 2.25.2 filtering by relation with bug None is not working properly. Unfortunatelly i cannot identify what is different from those that work :-( |
|
Here is another example of such case |
|
I am not able to reproduce using the given information. Also confusing: You started with "child of none" relationship when intering the issue, now there is "blocked by none" in your new screenshots. |
|
We have to find what is causing it then. For us having couple thousand tasks it is hapening for some of them. There was a theory from one colegue that child-parent is returning tasks that are "in the middle" meaning have parent and have child. I did not test that theory yet though. About different relation. Yes blocked by is custom one with id 1001 and 1000 for is blocking (oposite of blocked by). It works properly and its shown here more for a purpose of showcasing that same issue applies to other relations not only parent-child but possibly to all of them |
|
OK so one of our testers managed to find simple repro: Let me know if you manage to repro it as well please. |
|
I tried according 0026761:0066079 |
|
@sadovsf, I was not able to reproduce. |
|
Could it be database issue maybe? We have this problem on both of our instances we are using internaly. |
|
You can enable database logging and look at the statements that are executed in function |
|