Bug 876189 - [RFE]--[cf-beta] Documentation Topic: General group feedback
Summary: [RFE]--[cf-beta] Documentation Topic: General group feedback
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Documentation
Version: 6.0.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: Unspecified
Assignee: Athene Chan
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-13 14:21 UTC by Michael Hood
Modified: 2018-11-29 19:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-09 15:40:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michael Hood 2012-11-13 14:21:56 UTC
Description of problem:

Group label validation:
  Group names can contain spaces -- I'd prefer thay not.

  Group names can not contain a period -- I'd prefer that they could.

NOTE: See the "sets" comment in my prior Case update. That applies to
much of what follows.

Group labels & descriptions with multiple admins:
  As with a lot of things in this business, groups is an area that can get
  out of hand. It could, worst case, become a trash pit with thousands
  of system groups where nobody knows who owns or uses individual ones. 
I'm
  not accusing this is an original invention -- the concept of data as a
  trash-pit. Again, it is a regular phenomenon in this business.



Version-Release number of selected component (if applicable):

1.1


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:

Group label validation:
  Group names can contain spaces -- I'd prefer thay not.

  Group names can not contain a period -- I'd prefer that they could.

NOTE: See the "sets" comment in my prior Case update. That applies to
much of what follows.

Group labels & descriptions with multiple admins:
  As with a lot of things in this business, groups is an area that can get
  out of hand. It could, worst case, become a trash pit with thousands
  of system groups where nobody knows who owns or uses individual ones. 
I'm
  not accusing this is an original invention -- the concept of data as a
  trash-pit. Again, it is a regular phenomenon in this business.





Expected results/ Customer expectation:

However, to deal with this, we use rules. From you, we need the
  ability to assist staff in complying with whatever rules we come up
  with.

  At this time, not having any idea of what our implementation rules
  would actually be, my best idea is that you provide that "javascript
  hook" that we spoke about during Red Hat's site visit. That is, I need
  a stable insertion point where I can have javascript do things (e.g.,)
    - when a new group is created ... like pre-populating the
      description field with text that identifies whoever created the
      group
    - in the list of displayed systems, I may prefer to disable the
      ability to add or remove systems for certain groups
    * the example list could go on a while. I'd really like that
      javascript hook



Additional info:

Comment 2 Dan Macpherson 2013-02-01 06:38:48 UTC
Hi Michael, just want to follow up on this bug. Is this targeted to anythin specific in the System Engine User Guide.

Comment 3 Mike McCune 2013-08-16 17:59:41 UTC
getting rid of 6.0.0 version since that doesn't exist

Comment 5 Dan Macpherson 2013-10-09 15:40:18 UTC
This seems like a legacy bug from System Engine Guide. Plus it's been ages without a response. Closing it.

Comment 6 Andrew Dahms 2017-05-11 12:04:51 UTC
Clearing old needinfo request.


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