Allow to manage and subscribe to incidents - #1392
Conversation
b67ee1d to
d467e78
Compare
|
Please mention the required PR Icinga/icinga-notifications-web#472 in the description. |
|
One more thing I noticed: once you subscribe to and then unsubscribe from an incident in the incident detail view, subscribing again is not possible and throws an error, because the unsubscribe removes the incident_contact DB entry entirely. |
As discussed in person, this an unrelated bug, caused by the |
55cbf41 to
243c34d
Compare
nilmerg
left a comment
There was a problem hiding this comment.
Looking at this I noticed a flaw in my previous idea how the new component is integrated here. It relies on a few presumptions that are either incompatible or simply wrong:
- The user acknowledging needs a matching notifications contact
- This is not always true and we have no idea to identify this as intentional or not, an additional permission should solve this
- The acknowledgement form still allows to declare an expiry time
- But there's no way for Icinga DB to remove a manager, Icinga/icinga-notifications#478
- The acknowledgement form still allows to disable the sticky flag
- Let's hide this option for users that have the new manage permission and are a contact in notifications
- Enabling icinga notifications web does not mean it's configured, but this should be a requirement and be easy to answer to decide what to offer
- The module being enabled is not enough, db web knows about a working notifications component, so this should be the condition instead
- incident is already an outdated term so I don't want to see it here. It is also of no meaning to users which have no access to the configuration UI anyway, so we should rather focus on proper representation what the effect of acknowledge now is and what subscribe means compared to the legacy notifications feature. A seamless integration so to say, without the need for the user to know anything about Icinga Notifications.
This effectively makes it impossible to accidentally issue the query over and over. refs #1392
5c7bd3d to
0d9cb9f
Compare
|
The added When testing subscribe and unsubscribe in a detail view, the subscribe button may not change to unsubscribe. This is a bug in |
0c54b10 to
99d53b1
Compare
|
Please also extend |
nilmerg
left a comment
There was a problem hiding this comment.
Still have to test this, though. 😩 Didn't look at the UI in detail as well yet.
nilmerg
left a comment
There was a problem hiding this comment.
One, very small, thing left. You can directly sqash and rebase now.
Add a subscribe/unsubscribe option to `QuickActions` and `MultiSelectQuickActions`, and adjust the exitsing acknowledge/unacknowledge actions to also manage/unmanage.
Show subscribers and recipeints in a new section, highlighting the manager with a redisigned ack-badge. Rename the exitsing `Notifications` section to `Configured Contacts` to avoid confusion.
beae7dc to
b8a11f0
Compare

resolve #1358
requires Icinga/icinga-notifications-web#545
Add a new
Subscribebutton toQuickActions, to that allows to subscribe to the incident matching the Host/Service.The existing Acknowledge/Unacknowledge option also serves as manage/unmanage of the matching incident.
Users that have no notification contact configured will see an error message when trying to subscribe, and a warning when acknowledging.
A new
Notification Recipientssection is added to both Host- and Sevicedetail, showing the current recipients and subscribers. The manager is highlighted with the redesigned ack badge suggested in #1358 (comment).