Bug 5856 - difficult to find sessions in tlwebadm's session list
Summary: difficult to find sessions in tlwebadm's session list
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Administration (show other bugs)
Version: 4.4.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
: 2588 (view as bug list)
Depends on:
Reported: 2016-04-25 08:42 CEST by Henrik Andersson
Modified: 2023-09-12 16:03 CEST (History)
4 users (show)

See Also:
Acceptance Criteria:


Description Henrik Andersson cendio 2016-04-25 08:42:55 CEST
Today sessions are presented and grouped by user. Which only is desirable
when target for the use case is a user. If the use case is to gather
sessions by agents the current restraint is a burden.

We need to provide a better interface to query sessions with fine grained
control of the result. One example could be to use a filter function which
shows the result in a table:

[        ][ tlagent  ][          ][               ] [ FILTER ]

| User    | Agent     | Connected | Session Time   . . .
+---------+-----------+-----------+--------------- . . .
| tluser1 | tlagent01 |    Yes    |  8 days    
| tluser1 | tlagent02 |    Yes    |  2 days    
| tluser2 | tlagent02 |    Yes    |  1 hour
Comment 1 Samuel Mannehed cendio 2023-03-09 10:27:24 CET
After bug 8083, the list is no longer grouped by users. Each session gets a separate line in the table. The display number, agent, connection status and age will also be shown.

In my opinion, this bug is resolved by the changes made in bug 8083. Assigning to "---" for discussion.
Comment 2 Tobias cendio 2023-03-14 11:02:33 CET
When bug 8077 is resolved, it will be easier to find the session you're after. However, in a big cluster you might have thousands of sessions and being able to filter or sort the list would be beneficial. For smaller setups, we think the built-in Ctrl+F in the browser will be sufficient. 

A filter functionality is available in `$ sudo tlctl session list`.

Due to these reasons, we are lowering the milestone to LowPrio.
Comment 3 Pierre Ossman cendio 2023-09-12 13:06:37 CEST
*** Bug 2588 has been marked as a duplicate of this bug. ***

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