You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Nick Couchman (Jira)" <ji...@apache.org> on 2024/04/18 17:13:00 UTC

[jira] [Closed] (GUACAMOLE-1866) Improvements to the "Recent connections" section

     [ https://issues.apache.org/jira/browse/GUACAMOLE-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Couchman closed GUACAMOLE-1866.
------------------------------------
    Resolution: Implemented

> Improvements to the "Recent connections" section
> ------------------------------------------------
>
>                 Key: GUACAMOLE-1866
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1866
>             Project: Guacamole
>          Issue Type: New Feature
>          Components: Documentation, guacamole-client
>            Reporter: Julien Lejeune
>            Assignee: Nick Couchman
>            Priority: Trivial
>             Fix For: 1.6.0
>
>
> The "Recent Connections" section takes some place on the Guacamole homepage, but I have the feeling that it is not useful for all users, only for those who mostly connect to the same few connections.
> This comes from the assumption that the "Recent Connections" section only shows the five last connections, which is what I have seen so far. Let me know if I am wrong.
> So, I would suggest either of those :
>  * Allow a user or an administrator to remove or hide the "Recent Connections" section.
>  * Improve the usefulness of the "Recent Connections" section so it is useful to more users. For example, it would be nice to allow a user to remove a connection showing in the "Recent Connections" section if the user does not need this suggestion anymore. Also, when a connection is removed that way, the sixth last connection could come back again in the "Recent Connections" section.
> I am not a developer, so I am not sure how to implement it myself, but I would be open to try.
> First, I would like to read what you all think of those suggestions and where the discussion goes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)