Here’s a look back at what we worked on in sprint 6. To learn more about what we released, check out our June product updates blog post. 

HIGHLIGHTS

New trips view. 

Now, when you’re on a trip, you’ll see it listed under “Current trip” in your dashboard. Upcoming trips and past trips also have their own dedicated sections. This new UI shows each type of trip with different levels of emphasis.

6 IMPROVEMENTS

1. We released a new-and-improved layout for the bookings page.
2. We now display dates in a consistent long format. This is based on your location, so it will be more intuitive whether 6-9-2024 is June 9 or September 6, depending on how you format dates locally.
3. We also improved the place detail view. You can now see blocks associated with the place, and start booking directly from the place detail page. 
4. We improved the logic of trip naming to make it easier to find trips from booking confirmations. Before, trips were automatically named based on the subject of the forwarded booking email. We’ve updated the logic so trip names will now be based on the flight, hotel, or event location. 
5. A click-saving improvement: Before, when someone created a block, none of the fields would auto-populate. Now, if you click “create block” in a day on the plan, it knows what the date is and auto-populates it. Saving clicks :)
6. The personal view filter will now filter out other peoples bookings and just show yours. 

4 BUGS

1. Previously, the block detail view showed trip participants instead of block participants. This has been fixed, so now you’ll see block participants displayed here. 
2. Before, if you logged in by typing in app.gathergo.co, you may be logged in and view a cached version of the trip. This has been fixed, so you’ll only see the latest version, no matter how you log in.
3. Sometimes, when ingesting a booking, if there was no end date, a fake one would be created. This has been fixed so you won’t see gibberish names anymore. 
4. Before, if a user received a block poll but was not already participating in the block, it would result in a 500 error code. This has been fixed, so you shouldn’t see error codes going forward.