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
On the trip admin tab of a trip, there is a (wonderfully useful) "also on" section for each participant showing other trips they are signed up for and linking to them. These come in especially handy when managing participants that (somehow, inexplicably) have signed up for 3 trips on the same day, and more commonly when managing the waitlist as you pull participants up. To make this even smoother, I'm suggesting we add the day/date in parentheses to each "also on" trip, so that I don't have to click a link and see what day that other trip is. This is an extremely minor QoL request, but I spent a lot of time this week managing waitlists for trips and was thinking it would be a nice to have.
The text was updated successfully, but these errors were encountered:
Sure, that sounds like a very sensible (and very easy) QoL improvement. There's a somewhat limited amount of room for such a parenthetical. Would a 3-day day of the week abbreviation work well enough? (The "Also on" window is a sliding window that only covers a few days before & after a trip).
So, for example, this participant on a Thursday trip:
On the trip admin tab of a trip, there is a (wonderfully useful) "also on" section for each participant showing other trips they are signed up for and linking to them. These come in especially handy when managing participants that (somehow, inexplicably) have signed up for 3 trips on the same day, and more commonly when managing the waitlist as you pull participants up. To make this even smoother, I'm suggesting we add the day/date in parentheses to each "also on" trip, so that I don't have to click a link and see what day that other trip is. This is an extremely minor QoL request, but I spent a lot of time this week managing waitlists for trips and was thinking it would be a nice to have.
The text was updated successfully, but these errors were encountered: