Bug 1263672 - [RFE] Ancestor tag hierarchy should potentially be checked/highlighted when assigning an object on a descendant tag.
Summary: [RFE] Ancestor tag hierarchy should potentially be checked/highlighted when a...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 3.6.0
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-16 11:55 UTC by Lukas Svaty
Modified: 2019-04-28 09:18 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-10-10 15:34:45 UTC
oVirt Team: UX
Embargoed:
ylavi: ovirt-future?
pnovotny: testing_plan_complete-
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Lukas Svaty 2015-09-16 11:55:02 UTC
Description of problem:
See BZ#1201403 comment#1. 

Tag parent: parent
Two children: child-1, child-2

When adding tag 'parent' to VM and ticking the checkbox close to 'parent', checkboxes with 'child-2' and 'child-1' are left empty. This may lead to admin believing in not functional hierarchy or other behaviour than what was introduced bug BZ#1201403.

Resolution for this should be to ticking all the checkboxes of child tags with the parent for more user friendly behaviour.


Version-Release number of selected component (if applicable):
rhevm-webadmin-portal-3.6.0-0.15.master.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create tag hierarchy with parent 'parent' and children 'child-2' and 'child-1'
2. Assign tag 'parent'

Actual results:
Only tag 'all' is checked, and his child nodes are not automatically checked.

Expected results:
Tags 'child-2' and 'child-1' should be checked while 'parent' is checked

Comment 1 Einav Cohen 2015-09-17 12:22:03 UTC
if anything, it should be the other way around (i.e. ticking 'child 1' should potentially automatically tick 'parent'). 

I will give a concrete example to clarify:

Let's say that we have the following tags hierarchy:

-- USA
---- New York
---- LA

The issue that bug 1201403 fixed is that if you are searching for e.g. "VMs: tag = USA", then it will return (also) VMs tagged with 'New York' and/or 'LA', which makes sense because VMs 'located' in New York or in LA are located in the USA. 

If I am tagging a VM with 'USA', I don't want it to be automatically tagged with 'New York' and with 'LA'; first of all, it doesn't make sense (a VM cannot be located in both New York and LA; moreover, maybe this VM is located in 'Boston', so marking it with 'New York' and 'LA' is very misleading. 

However, if I am tagging a VM with 'New York', it is for sure in the 'USA', therefore we can automatically check it (or highlight it or something similar) with 'USA'. 

[updated BZ subject accordingly]

Comment 2 Greg Sheremeta 2017-11-30 17:24:31 UTC
I find the hierarchical tag concept confusing in general. Perhaps it should work more like gmail labels do.

Comment 3 Greg Sheremeta 2018-10-10 15:34:45 UTC
Unfortunately we don't have capacity to work on this.


Note You need to log in before you can comment on or make changes to this bug.