Hi! Thank you for your feedback. It’s great to hear that you’ve taken all the points into account. I’m eagerly awaiting the opportunity to move some of my complex projects from Airtable to Baserow.
Additionally, if you need any assistance in testing, discussing, or demonstrating user cases related to the ‘group by’ feature, I am more than willing to help in any way I can.
Thanks, we appreciate your support @Alexander 
Hey @Alexander, thank you once again for the comprehensive feedback on group by!
We’ve discussed your ideas that are not yet in our pipeline, and here are the updates:
#4: Placement of group titles
We plan to introduce an option that allows our users to select how they prefer groups to be stacked - vertically or horizontally. Refer to this issue for more details: Horizontal stack group by mode (#2436) · Issues · Baserow / baserow · GitLab
#5: Freezing the Primary field:
As I mentioned before, we plan to add the ability to freeze columns in general, and we have also added a point to this issue to make it work with the group by function as well: Pin/freeze columns in a table (#1953) · Issues · Baserow / baserow · GitLab
#8: Group By to work with Formula and Relation fields:
#9: Changing orders in a grouping by setting
Yes! For both groups and filters, we plan to make it possible to change orders using drag and drop: Change order of group by (#2434) · Issues · Baserow / baserow · GitLab
#10: Manual sorting (notion like)
We love this idea, and and will make it possible to manually sort the order of groups in ‘group by’: Manual sorting of groups order in group by (notion like) (#2435) · Issues · Baserow / baserow · GitLab
All your requests have been accepted. Thank you for helping us improve Baserow. 
Hi! Good to hear that!
If you need any feedback for the planned UI/UX, I am ready to help
Hi, Olga! Any updates on when could be these points get ready?
Hi @Alexander, all these issues have different priorities, which you can view in the Weight field:
Issues are sorted by weight here, from highest to lowest priority: https://gitlab.com/baserow/baserow/-/issues/?sort=weight_desc&state=opened&label_name[]=accepted%20📆&first_page_size=20. Make sure you have Weight selected here:
After using this workaround, how can I have temporary group sums?
@olgatrykush Hi, Olga!
I just wanted to kindly remind about this topic. I’m eager to migrate my projects from Airtable to Baserow, but without this functionality, my team might not have all the tools they need to work effectively. Points 1-8 are especially crucial for the migration, while points 9 and 10 are not as urgent.
I’ve checked GitLab, and as I understand, these points haven’t reached a stage of active development yet. If possible, could you discuss with the development team about raising their priority? I feel like these are the features that make Airtable and Notion so appealing, and it would be great to see them fully realized in Baserow as well.
Hey @Alexander, due to the high volume of requests and new feature ideas, we can’t significantly reprioritize features right now. To be honest, I don’t expect all features 1-8 to be released this year. Unfortunately, some of them have a low priority, and this is unlikely to change much.
Anyway, I’ll discuss your request with the team.
Ok! Thanks for answering) I’ll keep my fingers crossed to see it as soon as possible!
Hello Olga,
I hope you’re doing well. I continue to be impressed by how Baserow is developing — it’s clearly moving in a great direction, and I really appreciate the work your team is doing.
Reflecting on what I’ve shared earlier, I wanted to gently highlight that two features, in particular, feel especially important for real-world use:
These two functionalities are key to working smoothly with large datasets.
For example, in Airtable, grouping by month, product, or client makes it easy to collapse everything and focus only on the relevant sections. Without this in Baserow, grouped views can quickly become overwhelming as the data grows — especially when there are many records.
Imagine a view with just 5 groups, and each group contains 100 rows — that’s 500 rows on the screen at once, all expanded. Important groups often get pushed far down the page, and it becomes difficult and time-consuming to locate and work with the data you actually need.
This is exactly why users value the GroupBy functionality in Airtable so much — it allows them to collapse large sections, quickly find the group they need, and focus only on that segment. It’s efficient, clean, and essential for productivity.
In addition, summary rows within each group allow users to immediately see key metrics — totals, counts, averages — which means they can often make decisions without even opening the group. And when deeper exploration is needed, they can simply drill down into subgroups, each with its own summary. This nested control — collapse inside collapse — makes even complex datasets easy to work with and keeps the interface clean and user-friendly.
In my case, this has been one of the main reasons I haven’t yet been able to move some projects over to Baserow — not due to missing core features, but rather due to how challenging it can be to navigate large grouped datasets.
And I believe this isn’t a unique challenge — many other teams and users may experience similar limitations when trying to adopt Baserow for large datasets.
If these two features were added, I really think it would be a significant step forward, and would bring more business users to Baserow!
Thanks so much again, and I’d be truly grateful if you could pass this along to the product team.
Hey @Alexander, we know how important these two features are and we will get to them:
The problem is that lots of new issues/requests are constantly popping up and some older requests get pushed down the priority list. 
Great to hear from you! I hope you’ll be able bring it to a higher priority)