You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deleting a pipeline that sends notifications, the messages are no longer available in the notifications overview.
However, the number of unread notifications remains and is not reset.
How to reproduce?
see above
Expected behavior
From my point of view there are two alternatives:
a) the notification counter is reset as well
b) the notifications are not deleted automatically when removing the associated pipeline
Additional technical information
No response
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered:
Hi @bossenti
Currently, notifications are bound to a pipeline so that notifications are not shown if a pipeline is no longer present. I would see two options to solve this:
Notifications that belong to a pipeline are deleted once the pipeline is deleted.
We rewrite the notification module so that notifications are not bound to a pipeline, but could potentially also be created by other parts of the application. Notifications in the notification view would then not be organized by pipelines, but would include all notifications assigned to the user and maybe could be filtered by a notification type.
Since I think existing notification should not just disappear as in option 1, I tend to prefer 2. What do you think?
I agree with you that option 2 is the way to go hear.
But with the current implementation it is not possible to see/access the notifications once the pipeline is deleted right?
So until option 2 is implemented, option 1 might be good short-term solution? 🤔
Apache StreamPipes version
dev (current development state)
Affected StreamPipes components
Backend, UI
What happened?
When deleting a pipeline that sends notifications, the messages are no longer available in the notifications overview.
However, the number of unread notifications remains and is not reset.
How to reproduce?
see above
Expected behavior
From my point of view there are two alternatives:
a) the notification counter is reset as well
b) the notifications are not deleted automatically when removing the associated pipeline
Additional technical information
No response
Are you willing to submit a PR?
None
The text was updated successfully, but these errors were encountered: