MantisBT - TestLink
View Issue Details
0008105TestLinkFilters - Test Specificationpublic2017-10-12 18:392018-04-14 09:04
LinuxRed Hat Enterprise Linux Server7.1 (Maipo)
1.9.16 (2016 Q4) 
1.9.17 (2018 Q1) 
0008105: Test Specification Filter by Custom Field - REQUIRED ISSUE
I have a project that use personalized field available for test case.
It is set for test specification design and required field.

Whe I try to use the filter it require to complete the field but that field is not relevant for the searching because some time I don't know what is suppose to be the value.
1) Configure a presonalized field for TestCase with:
- Type: Radio
- Posible Values: value1|value2|value3
- Available for: Test Case Specification
- Display in Test Case Executions: Yes
2) Configure a project with that persolized field.
3) Execute a Test Case Specification filter without selecting the personalized field recently configured.
PD: I have Spanish language configured in my installation and I can make wrong mention of the field above.
Attached the filter Message when I tried to execute the a search.
I tested with Chrome where the problem happend, but it doen't happend in Internet Explorer.
No tags attached.
child of 0007817closed fman Availables hot-fixes for 1.9.16 & How To get full fixed package from GitHub 
jpg FilterMessage.jpg (32,125) 2017-10-12 18:39

jpg FieldConfiguration.jpg (37,361) 2017-10-12 18:40

png Screen Shot 2017-10-15 at 10.49.01.png (68,929) 2017-10-15 08:49
Issue History
2017-10-12 18:39ewmartinezNew Issue
2017-10-12 18:39ewmartinezFile Added: FilterMessage.jpg
2017-10-12 18:40ewmartinezFile Added: FieldConfiguration.jpg
2017-10-14 15:27fmanNote Added: 0026928
2017-10-15 08:49fmanNote Added: 0026931
2017-10-15 08:49fmanFile Added: Screen Shot 2017-10-15 at 10.49.01.png
2017-10-15 08:50fmanAssigned To => fman
2017-10-15 08:50fmanStatusnew => feedback
2017-10-15 08:50fmanNote Added: 0026932
2017-10-15 08:52fmanQA Team - Task Workflow Status => TBD
2017-10-15 08:52fmanSummaryTest Specification Requires to use personalized field => Test Specification Filter by Custom Field - REQUIRED ISSUE
2017-10-15 08:52fmanDescription Updatedbug_revision_view_page.php?rev_id=5376#r5376
2017-10-15 08:52fmanDescription Updatedbug_revision_view_page.php?rev_id=5377#r5377
2017-10-15 08:58fmanNote Added: 0026933
2017-10-15 08:58fmanFixed in Version => 1.9.17 (2018 Q1)
2017-10-15 08:58fmanQA Team - Task Workflow StatusTBD => READY FOR TESTING
2017-10-15 08:58fmanStatusfeedback => resolved
2017-10-15 08:58fmanResolutionopen => fixed
2017-10-15 09:03fmanRelationship addedchild of 0007817
2017-10-17 16:34ewmartinezNote Added: 0026939
2018-04-14 09:04fmanNote Added: 0027313
2018-04-14 09:04fmanStatusresolved => closed

2017-10-14 15:27   
first option => do not use a radio and try with a list field
2017-10-15 08:49   
An import point is :
remember that you can configure a field a mandatory and may be the issue is that when using a field as FILTER the mandatory has to be ignored.

Please check the section regarding Assign Custom Fields where attribute AT PROJECT level are defined => see attached immage
2017-10-15 08:50   
Confirmed issue is rised when custom field has been defined as REQUIRED => going to fix soon
2017-10-15 08:58   
solved with [^]
2017-10-17 16:34   
Hi, I've tested the list option and it worked fine.
And I've implemented the change and it work fine with the radio buttom too.
2018-04-14 09:04   
release 1.9.17