Description of problem:
Search engine does not support tags heirarchy
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.Create 3 VMs vm1 , vm2 and vm3
2.Create a "all" tag
3.Create "israel" and "usa" tags as children of the "all" tag
4. associate "all" tag with vm1
5. associate "israel" tag with vm2
6. associate "usa" tag with vm3
7. search by "VMs:tag=all"
Actual results:
only vm1 is selected
Expected results:
All vm1 , vm2 and vm3 should be selected since "israel" and "usa" are nested tags under the "all" tag
Additional info:
This seems as a regression be for 3.5 so we have to consider if to backport according to patch complexity and risk
Functionality testing is at the moment blocked by BZ#1263633.
However from the UI point of view when clicking assign tags on Vm whole tree of tags is displayed. See example
Tag parrent: all
Two child: usa israel
When adding tag 'all' to VM and ticking the checkbox close to 'all' checkboxes with 'usa' and 'israel' are left empty. This may lead to admin believing in not functional hierarchi or other behaviour than what was introduced in this bug.
Resolution for this should be to ticking all the checkboxes of child tags with the parent for more user friendly behaviour. Moving back to assigned.
Do you think this is sensible scenario?
If you believe this should be solved in newly created bug, please move back to ON_QA and create new bug for this issue.
Lukas
The above (reported in comment 1) should be in a new created bug.
Since you are reporting on it, please open the BZ and add all needed information
Thanks