Problem:

Currently, when a user selects the 'Close all' option on the Alerts page for a specific team's Operations, the warning message displayed is generic and does not clearly specify whether the alerts being closed are limited to the selected filter or include all alerts in the instance. This behaviour is the same across the Alerts page, which we access from the 'Your work -> Alerts' section.

The warning messages users see are of the following types:

We've found 172 alerts to close. This process may take some time. 

We’ve found 9888 alerts, but we can only close up to 1000 alerts at a time. After this is done, you can close more.

Would you like to close 1000 alerts? 

This ambiguity can lead to unintended actions where users inadvertently close alerts for the entire instance instead of the intended team or filter-specific alerts.

What is required?

The 'Close all' option should close only the alerts returned by the selected filter. Alternatively, if the option is designed to close all alerts from the entire instance, the warning message should clearly state this to avoid any confusion. 

This clarity will help users understand the scope of the action they are performing and avoid unintended consequences.

Why is This Required?

1. Expectation vs. Outcome: When a user accesses a specific team’s Operations page and selects the 'Close all' option, the expectation is that only alerts for that particular team will be closed. However, the current functionality closes all open alerts across the instance.
2. Irreversible Action: Since there is no feature available to reopen closed alerts, mistakenly closing all alerts from the instance can create serious operational challenges, particularly for administrators.
3. User Experience and Error Prevention: Clear and precise messaging ensures that users are informed about the scope of their actions and prevents errors that could disrupt workflows or lead to data loss.