Bug #2900

Impossible to visualize more of 10 hosts selecting port forwarding destination

Added by Alessio Fattorini about 5 years ago. Updated about 5 years ago.

Status:CLOSEDStart date:
Priority:LowDue date:
Assignee:-% Done:

100%

Category:nethserver-firewall-base
Target version:v6.5
Security class: Resolution:NOTABUG
Affected version: NEEDINFO:No

Description

  • I try to make a new port forwarding rule
  • I select destination (see pfw1.png)
  • NethServer shows me only 10 hosts of 29
  • I can't go ahead and see others 19 hosts

I can't find arrows or paging for select another page of hosts, there is nothing below the hosts list

pfw1.png (27.4 KB) Alessio Fattorini, 10/07/2014 06:21 AM

pfw2.png (46.3 KB) Alessio Fattorini, 10/07/2014 06:21 AM

History

#1 Updated by Alessio Fattorini about 5 years ago

  • Tracker changed from Feature to Bug

#2 Updated by Giacomo Sanchietti about 5 years ago

Can't you use the search field?

#3 Updated by Davide Principi about 5 years ago

Yeah that's how it's expected to work: it's impossible to visualize more than 10 objects!

That interface assumes Admin knows the key (or any other prop, like Description) of the object she's searching for.

NOTABUG for me. Could you suggest an enhancement of the UI?

#4 Updated by Alessio Fattorini about 5 years ago

Yes you're right but visualize only 10 of 29 is still wrong, because I see search box like a filter not like a search (see user panel)
Suggestions for a better usability:
  • visualize all rows and filter with box above
  • not display any rows, but put search box in the center of the page with a text like "Search host by name, IP or MAC address"

#5 Updated by Davide Principi about 5 years ago

Alessio Fattorini wrote:

  • not display any rows, but put search box in the center of the page with a text like "Search host by name, IP or MAC address"

I'd like this solution, for large sets (more than N elements). If there are less than N elements, list them all, hiding the search box.

N = 10 ?

What do you think?

Edit: BTW, during design time, I found inspiration from this article:
https://medium.com/@mibosc/responsive-design-why-and-how-we-ditched-the-good-old-select-element-bc190d62eff5

Initially could be listed
  • Most Recently Used (MRU) objects
  • Special objects (based on context): Any, Roles
  • ...

#6 Updated by Alessio Fattorini about 5 years ago

Davide Principi wrote:

I'd like this solution, for large sets (more than N elements). If there are less than N elements, list them all, hiding the search box.

N = 10 ?

What do you think?

I agreed.

Edit: BTW, during design time, I found inspiration from this article:
https://medium.com/@mibosc/responsive-design-why-and-how-we-ditched-the-good-old-select-element-bc190d62eff5

Very interesting

#7 Updated by Giacomo Sanchietti about 5 years ago

  • Tracker changed from Bug to Enhancement
  • Status changed from NEW to TRIAGED
  • Priority changed from Normal to Low
  • % Done changed from 0 to 20

I'd like this solution, for large sets (more than N elements). If there are less than N elements, list them all, hiding the search box.

N = 10 ?

What do you think?

I agreed.

Me too.

#8 Updated by Davide Principi about 5 years ago

  • Tracker changed from Enhancement to Bug
  • Status changed from TRIAGED to CLOSED
  • % Done changed from 20 to 100
  • Resolution set to NOTABUG

We have to file a new enhancement related to this bug, with a new title and description.

This NOTABUG could be related.

Also available in: Atom PDF