Morten Brekkevold

#400 deals with the initial implementation of queuing for this

> NB! Double check that "close ticket externally -> close incident in Argus" is **always** a desired workflow. I would say it isn't. *Closing* incidents in Argus is usually something...

I'm not sure I understand from this how you actually set up the backend container (did you copy some Dockerfile or build one of your own, inspired by "what's out...

I don't get what this issue is trying to describe. Care to elaborate, @hmpf ?

#307 and #305 have been closed, so this is now unblocked for the backend. We do, however, need a corresponding issue for the frontend.

This is relevant as a sub-part of #121

SUNET is currently working actively on this. Tagging @paulopamplona as the manager of this work :)

My comment from #450: > Is there some way we could restructure this into a GitHub Actions workflow that produces a PR with an updated diagram if the ER model...

As in NAV's alert profiles, when configuring a subscription to queue notifications for a set time, there is a toggle to ignore incidents that have been resolved by the time...

1. I think there should be a separate event **type** for stateless incidents. Instead of creating a `STA` event, it should perhaps be something like `MSG`, which indicates this was...