Bug 999694

please provide more details/exmaple

How complex will it be to add this?

(In reply to Yaniv Dary from comment #4)
> How complex will it be to add this?

This needs to be discussed with the UXD team first, to see whether the user-experience design suggested here is valid and makes sense. 

To me personally - this doesn't necessarily make sense as-is, since we already have tags that allow us to, well, tag objects. I am not sure if we should create another completely-separate tagging-mechanism using colors. 

What I would consider is to allow associating tags with colors. 
Let's say that I have tag1 and I associate it with the 'blue' color. 
I would automatically paint blue the following: 
(a) 'tag1' itself (i.e. in the tags view or similar). 
(b) any object that is tagged with 'tag1' or with a descendant of 'tag1'. 
(c) any object that is associated with an object in (b) [e.g. if (b) contains 'host1' and 'VM1' runs on or pinned to 'host1' at the moment, 'VM1' will need to be colored as well]

Regardless of whether we are hooking into the existing tags mechanism or not, we need to create a UI and backend for associating an object with a color (or for associating a tag with a color), a logic for determining color for every object in the system, i.e. 'is this object colored or associated with any other colored object in the system?' (would have to be in the db-view level per object type or something similar - I don't see how this can be optimized performance-wise otherwise) and add UI support for colored grid-rows. 

From my perspective, this seems rather complex and should not be considered to any release earlier than 4.0. I also imagine that I would need some assistance for backend/db-related items.

This would help our environment too.  Another option that isn't quite as visually striking would be to add another column that shows what it's tagged.

This isn't conforming to UXD principles.
Closing as wontfix.
You can use the search to filter those out.