Feature Request: Option to Change Device Sort from Alphabetical to Port Number/Numerical on Network Topology

[neocharles]

Is there an existing issue for this?

• I have searched the existing open and closed issues

Is your feature request related to a problem? Please describe

The current implementation of the network topology view sorts devices alphabetically. This was based on the decision in #860 to standardize sorting. While alphabetical sorting may suit some use cases, it poses a challenge for network management purposes, where understanding physical connections is critical. Specifically, an option to sort by port numbers in numerical order would make it significantly easier to identify what device is connected to which port in real time, aiding in troubleshooting and system optimization.

For instance, when managing switches or large networks, having a clear, sequential view of devices based on port assignments helps streamline tasks such as cable tracing, port identification, and error resolution. Alphabetical sorting, on the other hand, often obscures this direct relationship between devices and their physical connections.

Describe the solution you'd like

Add a method to toggle the sort order for devices in the network topology view. This option could be available in the settings or as a dropdown toggle within the interface itself. Users should be able to choose between:

• Alphabetical sorting
• Numerical/port number sorting

If possible, this toggle should persist for user convenience (e.g., saved in user preferences or settings).

Describe alternatives you've considered

• Manually cross-referencing the alphabetical list with physical port connections, which is inefficient and error-prone, particularly in larger networks.
• Exporting device data and creating a custom mapping in a spreadsheet, which is time-consuming and not viable for dynamic or real-time changes.

Anything else?

This feature would primarily benefit network administrators and technicians managing medium to large networks where physical port mapping plays a significant role. Having a clear, port-based view aligns better with how hardware connections are physically arranged, reducing cognitive load and errors during maintenance or troubleshooting activities.

Am I willing to test this? 🧪

• I will do my best to test this feature on the netlertx-dev image when requested within 48h and report bugs to help deliver a great user experience for everyone and not to break existing installations.

Can I help implement this? 👩‍💻👨‍💻

• Yes
• No

[jokob-sk]

Thank you for the detailed explanation on why this is important.

This should be available in the next release. It would be great if you could test this. Can you please switch to the netalertx-dev docker image (backup everything at first or, ideally spin up a separate container with a separate db and config), in about 15 minutes (or after the last action finishes) from now?

Consider sharing the app on socials 🙂🙏

Thanks in advance,
j