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

Add interface to manually resolve an open Incident #96

Closed
lunkwill42 opened this issue Jul 2, 2020 · 1 comment
Closed

Add interface to manually resolve an open Incident #96

lunkwill42 opened this issue Jul 2, 2020 · 1 comment
Labels
discussion Requires developer feedback/discussion before implementation task

Comments

@lunkwill42
Copy link
Member

Once Uninett/Argus#73 is implemented, the frontend must provide the user with a function to manually resolve an open Incident.

For individual Incidents, this can be made accessible through the Incident details dialog box.

Manually closing an incident should not be easy to do by accident. There should also be the option to add a message string, explaining why an Incident was resolved manually.

@lunkwill42 lunkwill42 added discussion Requires developer feedback/discussion before implementation task labels Jul 2, 2020
@jorgenbele jorgenbele added this to To do in Argus Sprint #2 via automation Aug 7, 2020
@jorgenbele jorgenbele moved this from To do to Waiting on backend in Argus Sprint #2 Aug 7, 2020
@jorgenbele jorgenbele moved this from Waiting on backend to Done in Argus Sprint #2 Sep 14, 2020
@hmpf
Copy link
Contributor

hmpf commented Sep 15, 2020

This is implemented both in backend and frontend, closing.

@hmpf hmpf closed this as completed Sep 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Requires developer feedback/discussion before implementation task
Projects
No open projects
Development

No branches or pull requests

2 participants