Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interface improvements (buttons) #5057

Closed
2 tasks done
kosta880 opened this issue Jun 20, 2021 · 3 comments
Closed
2 tasks done

Interface improvements (buttons) #5057

kosta880 opened this issue Jun 20, 2021 · 3 comments
Labels
support Community support

Comments

@kosta880
Copy link

kosta880 commented Jun 20, 2021

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

Is your feature request related to a problem? Please describe.

Workflow problem. I am missing "interface-unity", and suggest some improvements.
Problems:

  • some pages under Firewall offer "+ Add" to add a rule or entry, some don't (Aliases being my biggest problem, when I have many aliases, always have to scroll to the bottom of the page to create new alias with the + sign).
  • "Apply Changes" - don't understand the need for it. I create or change the rule, I must apply changes. But I cannot cancel the change? What is the point having to apply then? Doesn't make much sense.
  • Apply changes remains only on the page where changes were made (e.g. Firewall rules)

Describe the solution you like
Add "+ Add" to:
Firewall -> Aliases
Firewall -> Categories
Firewall -> Shaper -> Pipes/Queues/Rules
Leave the small + sign at the end.

Add "Cancel" button, to revert the changes, if this is doable.
Move the Apply Changes out of the Firewall page to the top (left from the username) and let it sit there until confirmed when changes pending.

@kosta880
Copy link
Author

Sorry, seems I missed this one: #5047
Similar to my suggestion for Apply Changes.

@fichtner
Copy link
Member

  1. Please don’t merge different ideas in one collection ticket. It’s harder or impossible to get them done in practice. Discussions are going to be convoluted too.
  2. I’m going to close this, because it is a duplicate and you haven’t searched for issues as you stated.

@fichtner fichtner added the support Community support label Jun 20, 2021
@kosta880
Copy link
Author

My apologies. I will be more vigilant in the future and will not merge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support Community support
Development

No branches or pull requests

2 participants