Bug 742623 - Improve docs on compatible/mixed group descriptions
Summary: Improve docs on compatible/mixed group descriptions
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Documentation
Version: 4.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: ---
: ---
Assignee: Deon Ballard
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On: 742520
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-30 19:36 UTC by Deon Ballard
Modified: 2012-06-29 01:10 UTC (History)
3 users (show)

Fixed In Version:
Clone Of: 742520
Environment:
Last Closed: 2012-06-29 01:10:28 UTC
Embargoed:


Attachments (Terms of Use)

Description Deon Ballard 2011-09-30 19:36:08 UTC
+++ This bug was initially created as a clone of Bug #742520 +++

Go to Inventory, then click on compatible group and then on "New". Enter a name, then select resources.
Select all resources and finish. See the list of compatible groups on the next step not having the compatible group listed, as by adding all resources, a mixed group has been created.

While on one hand it is good to be a little bit more flexible than before, this also may result in a confused user.

We should 
- add a descriptive blurb on page 1 of the group creation wizard, that explains comp. vs mixed groups
- add a section in the docs
- re-think if we need the individual entries on the inventory tab for comp/mixed groups, as one may just create compatible +mixed groups on the "all groups" entry.

--- Additional comment from hrupp on 2011-09-30 15:32:36 EDT ---

http://docs.redhat.com/docs/en-US/JBoss_Operations_Network/3.0/html/Basic_Admin_Guide/sect-Basic_Admin_Guide-Managing_Groups-Defining_Groups.html 

does not talk about how a user can create a comp / mixed group.

In the old UI, this was explicitly chosen by the user.

Comment 2 Robert Buck 2011-11-28 21:44:13 UTC
Verified. Two tweaks:

a. /dictates/specifies
b. /andmixed/and mixed/

Deon fixed this already via direct conversation.


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