@epriestley that custom policy was intentionally set as the screenshots contain the names of people who may not want them on the internet (plus other event details and whatnot)

I destroyed F641702 and F641705.

Okay thanks

A few possible directions:

1. Leave as "Attending: ...". Then we would have to only include participants that actually accepted an invite. I assume that not all teams are very diligent about sending an RSVP to events, so there would be many events where no one or few people have accepted or declined. I also think that this does not really fit into the "Upcoming events" saved query, because as an invitee, I'd like to see all upcoming events I'm invited to, not just the ones I've accepted (which begs the question, how did I find the invite in the first place if the event didn't show up in my main saved query).
2. Switch to something like "Invited / confirmed: ...". I'd want to see events that I've been invited to, and ones that I've already said I'd attend. Because "invited" and "accepted" are two different statuses, I'd assume here we'd show both. If we do this, we'd have to probably figure out what to call a status that is invited and/or attending. Basically this would mean anyone that hasn't declined or been uninvited.
3. Third option is to completely decouple the idea that invited and attending are similar statuses. This would mean making 2 saved queries: "Invited" and "Attending" which would take the place of the previous "Upcoming Events" saved query.

Option 2 is probably the closest to a compromise between 1 and 3, but I can't think of any reason why 3 would be too much work. Maybe it would?

I think it's OK for the UI to show different stuff from the actual query fields -- it's OK to query by "Invited" but see "Attending" in the list. It's just confusing right now because it says "Attending: ..." but includes not-RSVP'd users.

"Upcoming Events" is also currently all events, not just your events, I think?

So I'd be inclined to do (1) first, but only change the list UI without changing any of the search/query stuff.

I think also allowing you to query for events that you (or other users) are attending is reasonable, but we don't need to pursue that right now since no one has actually asked for it, unless you want to.

A possible route for that would be with typeahead functions, so we'd still have one "Invited" field but you could type attending(epriestley) or declined(epriestley) or similar into it. The advantage of this approach is that we don't need to have 4 different fields; the disadvantage is that it's significantly more complex to implement.