Logical Flaw in "Select All" Action – Invitees View

Problem Description: There is a critical inconsistency in the Invitees view selection logic. When a status filter is applied (e.g., "Waiting"), the "Select All" action ignores the active filter and selects the entire database instead of the filtered subset.

Steps to Reproduce:

1. Navigate to the Invitees page.

2. Filter by a specific status (e.g., click the Waiting tab, which shows 283 contacts).

3. Check the "Select all" checkbox at the top of the list.

4. Click the link: "You have selected 25 contacts, do you want to select all contacts? Select All".

Current Behavior: The system selects all 720 contacts (the total count) regardless of the active "Waiting" filter.

Expected Behavior: The "Select All" action must be contextual. If the "Waiting" filter is active, clicking "Select All" should only select the 283 contacts corresponding to that status.

Impact & Risks:

• Operational Errors: Users trying to perform bulk actions (e.g., sending reminders) on "Waiting" contacts will accidentally target users in "Completed" or "Issues" statuses.

• User Experience: The current logic is counter-intuitive. Filters are meant to segment data for specific actions; breaking this segment during selection renders the filtering system useless for bulk operations.

Suggested Fix: Update the "Select All" scope to match the current filtered view. The confirmation message should dynamically update to: "Do you want to select all 283 contacts?"

Why this is a problem:

The primary purpose of the status tabs is to allow users to manage specific groups of invitees. By selecting the entire database instead of the filtered list, the system forces users to process contacts page-by-page (25 at a time) to avoid errors, which is highly inefficient for large datasets.