Bug with custom fields values filter in Test Specification

[mbeluet]

Voila le détail pour le bug 277303, au cas où tu voudrais poster sur teamst.

Hello,
We notice a problem that seems to be a bug...

For information we are using Testlink 1.9.3 (we were using Testlink 1.8.5 before).

The problem occurs in Test Specification folder. As we use some customs fields, we tried to use the filter that appears in 1.9.X release.
It appears that the filter seems not to work, depending on the filter choosed on Custom Fields results are not coherent.

It seems to be due to a conception problem in the filter (file lib\functions\treeMenu.inc.php, fonction filter_by_cf_values(), line 1466)
In the algorithm, it seems that it don't take into account the possibility of multiple version for a Test Case (as the custom fields is now connected to a Test Case Version and not to a Test Case).
More, If I have several version of the Test case with several values of Custom fields (If the value changed between 2 versions), which value will be taken ?

For me, I think, the conception of the algorithm miss something and maybe you should do a choice for example verify on the last test case version active to be able to have the correct value to filter on.

Thanks for your support.

[fman]

Please if you think is a bug then report it on the right place i.e. MANTIS., because dev team use Mantis as MAIN TOOL.
Please give detailed steps to reproduce (i.e a good test case) because without clear info, due to limited resources we work only on clear issues.

[mbeluet]

Ok,
The bug already exists in mantis with number 0004739

Thanks

[baldr]

I've made quick patch for this bug. Added to bug's comments there in mantis.