core
core copied to clipboard
opnsense
Add a Separator to NAT list page and rule page
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
- [x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
- [x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is including your motivation for the request, i.e. "For the purpose of [...] I am missing a solution that will [...]."
Describe the solution you like
Add a Separator to Port Forward list page and Rule list page(and some where need)as a row, The separator can be customized with a name and movable ,To make it easier to categorize items
Describe alternatives you considered
Additional context
we support categories for ordering purposes, you can find them in the top right corner.
I know this, But its not like what i say. or we can display a different background row color for different category items
I also think separators (just a labelled rows, to visually separate rules) would be very appreciated. Categories are nice, but not a replacement (If you filter for a category, you can't see complete rule ordering, if you don't, categories only add small color dots, which makes it hard to distinguish when you have a lot of rules)
As an example, I have ~70 different entities connected with IPSec. I need to maintain a set of rules (~5 rules per entity) for each of them, on the IPSec enc0 interface (so, ~350 rules on the same page). Managing 70 categories would be a pain, and choosing 70 visually distinct colors hard. Inserting separators between each of them would make the rule list much more readable
This issue has been automatically timed-out (after 180 days of inactivity).
For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.
If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.
