Bug 1006487 - Manual autodiscovery is confusing
Summary: Manual autodiscovery is confusing
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Usability
Version: JON 3.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ER02
: JON 3.3.0
Assignee: Jay Shaughnessy
QA Contact: Armine Hovsepyan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-10 17:15 UTC by Viet Nguyen
Modified: 2015-09-03 00:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-11 14:03:51 UTC
Type: Bug


Attachments (Terms of Use)
screenshot (149.25 KB, image/png)
2013-09-10 17:15 UTC, Viet Nguyen
no flags Details
run_autodiscovery (119.93 KB, application/octet-stream)
2014-09-05 15:18 UTC, Armine Hovsepyan
no flags Details
run_autodiscovery_pl (118.61 KB, application/octet-stream)
2014-09-05 15:18 UTC, Armine Hovsepyan
no flags Details

Description Viet Nguyen 2013-09-10 17:15:01 UTC
Created attachment 796082 [details]
screenshot

Description of problem:

1. "Manual Autodiscovery" sounds like an oxymoron.  What about just "Manual Discovery"?  

2.  This perhaps should be a first-class operation.  I'd like to see a button to trigger manual discovery on Platform view.

Comment 1 Jay Shaughnessy 2014-08-22 18:57:42 UTC
I agree that this is silly terminology and should be changed.  For me that's enough to satisfy this request.

A special case button?  I could live with it but that's a UX thing.

As a side note, if we really do work for this I think think the same sort of operation should exist on RHQ Agent resources.

Pushing due to time constraints.

Comment 2 Thomas Segismont 2014-08-22 21:12:00 UTC
(In reply to Jay Shaughnessy from comment #1)
> I agree that this is silly terminology and should be changed.  For me that's
> enough to satisfy this request.
> 
> A special case button?  I could live with it but that's a UX thing.
> 
> As a side note, if we really do work for this I think think the same sort of
> operation should exist on RHQ Agent resources.
> 
> Pushing due to time constraints.


What about just changing the display name of this operation to "Run discovery"? 

This operation is actually all but "manual". It triggers auto-discovery, but out of the standard agent schedule.

If the name satisfies everyone, the changes is very trivial and the fix can be pushed for ER2

Comment 3 Jay Shaughnessy 2014-08-26 16:05:10 UTC
Since you would not let this go I changed to "Run Autodiscovery" :)   I think we should keep the "Auto" just fr consistency with the "Autodiscovery Queue".

Any other enhancement (i.e. a button) should be created as a new RFE.


release/jon3.3.x commit eaf199722b103b98f9f04303364952d3c845d789
Author: Jay Shaughnessy <jshaughn>
Date:   Tue Aug 26 12:01:25 2014 -0400

    [1006487] Manual autodiscovery is confusing
    Changed to "Run Autodiscovery"

Comment 4 Simeon Pinder 2014-09-03 20:31:30 UTC
Moving to ON_QA as available for test with the following brew build:
https://brewweb.devel.redhat.com//buildinfo?buildID=381194

Comment 5 Armine Hovsepyan 2014-09-05 15:18:32 UTC
Created attachment 934840 [details]
run_autodiscovery

Comment 6 Armine Hovsepyan 2014-09-05 15:18:51 UTC
Created attachment 934841 [details]
run_autodiscovery_pl

Comment 7 Armine Hovsepyan 2014-09-05 15:19:14 UTC
verified in JON 3.3 ER02
screen-shots attached


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