When Discovery plugin is installed, users clicking on All Hosts might
find misleading not to find all hosts there. I was never thinking about
it as regular Foreman user (don't want to write "experienced"
While I can see his point, he's only encountering the issue because
downstream have decided to install discovery by default - most users
get exposed to the All Hosts button, and it's function, long before
they install Discovery.
I don't see a lot of options:
It doesn't make sense to rename All Hosts in core just to account
for a Plugin users may or may not have installed.
I'm not keen on using Deface (or similar) to re-write the menu entry
if Discovery is installed (on install, users might get confused as to
why the All Hosts link has apparently been deletedā¦)
Adding checkboxes or something to the /hosts page to include other
STI types will probably be overlooked by users, leading to the same
problem anyway.
So, while he has a point, I think this is a non-trivial problem with a
minimal gain for solving. Let's just document itā¦
Greg
Ā·Ā·Ā·
On 9 June 2014 11:44, Lukas Zapletal wrote:
> Hey,
>
> James brought interesting UI usability issue:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1105354
>
> When Discovery plugin is installed, users clicking on All Hosts might
> find misleading not to find all hosts there. I was never thinking about
> it as regular Foreman user (don't want to write "experienced" :-)
>
> Opinions? How should we handle that situation?
