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.

Sign up for GitHub

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

Jump to bottom

Rewrite Event Rule Configuration #171

Open
nilmerg opened this issue Apr 9, 2024 · 0 comments · May be fixed by #159
Open

Rewrite Event Rule Configuration #171

nilmerg opened this issue Apr 9, 2024 · 0 comments · May be fixed by #159
Assignees
@raviks789
Labels
area/view Affects an entire view enhancement New feature or improvement

Comments

@nilmerg
Copy link
Member

nilmerg commented Apr 9, 2024

The current implementation of the event rule configuration is composed of several separate forms.

This poses an unnecessary limitation as it heavily relies on auto submission and caching. It is not feasible to further develop features based on it.

The goal is to replace it, so that a single form is used, auto submission is reduced to a minimum and the cache is completely optional and removable.
@nilmerg nilmerg added the enhancement New feature or improvement label Apr 9, 2024
@nilmerg nilmerg added this to the Beta milestone Apr 9, 2024
@nilmerg nilmerg linked a pull request Apr 9, 2024 that will close this issue
Event rule config enhancement #159
Open
@nilmerg nilmerg added the area/view Affects an entire view label Apr 9, 2024
@nilmerg nilmerg removed this from the Beta milestone May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@raviks789 raviks789

Labels
area/view Affects an entire view enhancement New feature or improvement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Event rule config enhancement Icinga/icinga-notifications-web
2 participants
@nilmerg @raviks789