Bug 796182 - Selecting Synchronization Results History id's in a content source unselects automatically after few seconds
Summary: Selecting Synchronization Results History id's in a content source unselects ...
Keywords:
Status: NEW
Alias: None
Product: RHQ Project
Classification: Other
Component: Content
Version: 4.3
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-22 12:45 UTC by Sunil Kondkar
Modified: 2022-03-31 04:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Sunil Kondkar 2012-02-22 12:45:27 UTC
Description of problem:

After creating a content source, tried to select individual/all Synchronization Results History id's in the checkboxes. After few seconds the selected id's get unselected automatically after few seconds (2 or 3 seconds)

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

Build Version: JON 3.0.1.GA RC5 (Build Number: dd8a001:fbca611)
Browser: Firefox 3.6.3
Database : PostgreSQL 8.3.8

How reproducible:

Always

Steps to Reproduce:

1. Login to UI
2. Navigate to Administration->Content->Content Sources
3. Click on 'Create New' button.
4. Click on 'Local Disk Storage Content Source'.
5. create a content source specifying some directory at platform.
6. Click on 'Synchronize' button few times. It will display status and ID's in 'Synchronization Results History' section.
7. Select and individual id or select all id's by clicking in the 'ID' checkboxes.
8. After 2 or 3 seconds the selected id's get unselected automatically.

  
Actual results:

Selected Synchronization Results History id's get unselected automatically.

Expected results:

The Synchronization Results History id's should not get unselected automatically.

Additional info:

Comment 1 Mike Foley 2012-02-22 15:30:57 UTC
triage 2/12/2012 ccrouch, stefan_n, mfoley


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