Bug 641184 - Groups: Cannot modify Description of a Group if tags are populated
Summary: Groups: Cannot modify Description of a Group if tags are populated
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Core UI
Version: 4.0.0
Hardware: All
OS: Linux
low
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Corey Welton
URL:
Whiteboard:
Depends On:
Blocks: rhq4 gwt-groups
TreeView+ depends on / blocked
 
Reported: 2010-10-08 00:14 UTC by Corey Welton
Modified: 2011-05-24 01:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-24 01:09:20 UTC


Attachments (Terms of Use)

Description Corey Welton 2010-10-08 00:14:47 UTC
Description of problem:
As long as a group is "tagged" with some value, the description fails to be modified.

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


How reproducible:


Steps to Reproduce:
1. Create a group, either mixed or compatible
2. Navigate to the view for this group
3. Edit the description field multiple times -- change the values a variety of different ways, "foo", "bar", "baz".  Note successful modification.
4. Click the green tag "+" above and add some string as a tag
5. Repeat step 3 - note results
6. Remove tag(s)
7. Repeat step 3 - note results

Actual results:
As long as a group is tagged, the Description field cannot be modified. Removing those tags allows it to be modified.

Expected results:
Some normal user workflow

Additional info:
* If tagging doesn't make it into the final product, we can close this out.  Until then, tagging can cause a failure to edit these as appropriate.
* I have not yet tried this for individual resources.  May occur there too

Comment 1 Jay Shaughnessy 2011-02-14 15:02:30 UTC
Could not reproduce.

Comment 2 Corey Welton 2011-02-14 19:19:45 UTC
Seems to work now.  Verified.

Comment 3 Corey Welton 2011-05-24 01:09:20 UTC
Bookkeeping - closing bug - fixed in recent release.


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