2.3.3 Patchnotes question
-
Hi all,
I'm curious about
Do not sort interface menu entries for consistency with other GUI instances #6753
and the info in the corresponding bugtracker item.
https://redmine.pfsense.org/issues/6753
As I read the last messages in redmine, I was under the assumption that
Commit reverted.
would indicate, that the change was rolled back and not be brought into the 2.3.3 Update.
It may seem trivial to most users, but we run datacenter clusters with multiple VLANs in the range of 20-40 interfaces and that change would be really quite annoying. We named the project VLANs according to their VLAN-ID and project name vXXX_name and would now have to "search" in the menu opposed to the normal sorted order, where you find an interface quite easily. We already were hoping the ticket would result in e.g. the Firewall Rules Dropdown (that only appears if there are too many interfaces for tabbing) be sorted accordingly, as this is hard to search in day to day operations.As it states in https://redmine.pfsense.org/issues/6753#note-6 we have quite similar setup, where VPN interfaces added to projects are sorted to their project interface by naming it accordingly. I can see the initial thought behind not sorting as the order of the interfaces is relevant with CARP setups, but as the interfaces/assignment screen already shows the "true" order - that IMHO is irrelevant in other day to day operation usage - I'd really like to see some sort of switch in the UI to activate sorting of the main menu as well as e.g. the rules dropdown or other dropdown menus that include the interfaces to sort for better overview.
If someone could clarify the last message of this ticket (change reverted) to the changelog of 2.3.3 that'd really be appreciated.
Thanks a lot for the hard work!Greets,
Jens -
It's just an oversight in the changelog. The commit was reverted after the notes were made and it didn't get updated. I removed the note.
-
Thanks a ton jimp,
was worried about that one. :)
Greets
