# šŸ”® Fibery roadmap for Feb-April 2023 **URL:** \ **Category:** News & Announcements\ **Created:** [February 8, 2023, 8:56am UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940 "2023-02-08T08:56:23Z")\ **Posts on this page:** 20\ **Page:** 3
**Author:** ![Jose\_Quesada](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jose_quesada/32/5458_2.png) [@Jose\_Quesada](https://community.fibery.io/u/Jose_Quesada)\ **Post date:** [April 5, 2023, 2:30pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/48 "2023-04-05T14:30:45Z")
Is there any threads on fibery roadmap and the chatGPT api? I totally get it that itā€™s a big topic, but others (notion?) are rushing ahead, and I see [some parts of the docs referring to prompts](https://the.fibery.io/@public/Public_Roadmap/Roadmap_Item/AI-Assistant-via-ChatGPT-API-170). ---
**Author:** ![tpaktop](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/tpaktop/32/6394_2.png) [@tpaktop](https://community.fibery.io/u/tpaktop)\ **Post date:** [April 5, 2023, 2:44pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/49 "2023-04-05T14:44:47Z")
Itā€™s just got released see [April 3, 2023 / šŸ‘½ Fibery AI (Create Space with AI help, Text Assistant, AI in Automations) - News & Announcements / Changelog - Fibery Community](https://community.fibery.io/t/april-3-2023-fibery-ai-create-space-with-ai-help-text-assistant-ai-in-automations/4228/19) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 5, 2023, 2:52pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/50 "2023-04-05T14:52:24Z")
Yes, it is already there šŸ™‚ > **[Fibery AI](https://fibery.io/ai)** > > Use Fibery AI Assistant to brainstorm ideas, improve writing, automate work, and experiment with your process ā€” in the same context where you work and think. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [April 7, 2023, 6:14am UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/51 "2023-04-07T06:14:21Z")
6 posts were split to a new topic: [GPT 3.5 vs GPT 4](https://community.fibery.io/t/gpt-3-5-vs-gpt-4/4268) ---
**Author:** ![tpaktop](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/tpaktop/32/6394_2.png) [@tpaktop](https://community.fibery.io/u/tpaktop)\ **Post date:** [April 7, 2023, 1:45am UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/57 "2023-04-07T01:45:14Z")
Did you see compression prompts for LLM ? One example - [https://twitter.com/piratewires/status/1643673273723650048?s=46&t=DO575TBj5m8z5ebQ7oVdBg](https://twitter.com/piratewires/status/1643673273723650048?s=46&t=DO575TBj5m8z5ebQ7oVdBg) It allows to reduce used tokens a lot. Havenā€™t experimented with it enough to see how lossless itā€™s but I guess itā€™s a matter of correct prompt. ā€œInventing assembler againā€ )) Thinking out loud you can probably fine-tune a model to an algorithm if itā€™s giving good results. That there should be no need to pass the original algorithm to the model every-time. Though that is just a hypothesis. ---
**Author:** ![jondkinney](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jondkinney/32/6061_2.png) [@jondkinney](https://community.fibery.io/u/jondkinney)\ **Post date:** [April 28, 2023, 8:18pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/58 "2023-04-28T20:18:21Z")
Any progress on the table improvements? ---
**Author:** ![Tim\_Kim](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/tim_kim/32/1619_2.png) [@Tim\_Kim](https://community.fibery.io/u/Tim_Kim)\ **Post date:** [April 28, 2023, 10:25pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/59 "2023-04-28T22:25:16Z")
Iā€™m with jondkinney! We have about 10 users on clickup. We really want to move to [Fibery.io](http://Fibery.io) but are waiting for the table improvements. Without grouping it becomes to hard to navigate and understand rows at a glance. ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [April 29, 2023, 7:08am UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/60 "2023-04-29T07:08:15Z")
Same, the table improvements will impact our set-up so much that we ideally postpone the go live of our customers. Because we need to do a lot of rework in views after the release. ---
**Author:** ![Tommy\_Hedley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/tommy_hedley/32/6468_2.png) [@Tommy\_Hedley](https://community.fibery.io/u/Tommy_Hedley)\ **Post date:** [April 29, 2023, 2:44pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/61 "2023-04-29T14:44:44Z")
I would like to see table improvements as well! I love all of the other improvements that weā€™ve got recently, but a fully featured table view would get rid of a lot of janky report views and make my whole process much cleaner. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [May 2, 2023, 6:56am UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/62 "2023-05-02T06:56:34Z")
@jondkinney @Tim_Kim @YvetteLans @Tommy_Hedley Not much to show about tables, we are still migrating to AG Grid and even MVP is at least a month aheadā€¦ ![2023-05-02 09.54.44](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/0321885c04f166693b932f03266fa43620709555.gif) ---
**Author:** ![ccollins](https://avatars.discourse-cdn.com/v4/letter/c/bbe5ce/32.png) [@ccollins](https://community.fibery.io/u/ccollins)\ **Post date:** [May 2, 2023, 1:44pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/63 "2023-05-02T13:44:51Z")
This looks great! Will grouping by non-relation fields be possible, like rows in board view? Or is grouping only other databases like in list view? ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [May 2, 2023, 1:48pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/64 "2023-05-02T13:48:21Z")
There is no limit to add that, we will do it in next iterations. But again, first we will just match existing functionality with some improvements, then iterate fast (I hope) ---
**Author:** ![JochenXYZ](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jochenxyz/32/6575_2.png) [@JochenXYZ](https://community.fibery.io/u/JochenXYZ)\ **Post date:** [May 5, 2023, 3:15pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/65 "2023-05-05T15:15:44Z")
is there already a date for the release of these new tables. Missing this feature and waiting for it to test. ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [May 5, 2023, 3:42pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/66 "2023-05-05T15:42:54Z")
> [@crystal\_ball Fibery roadmap for Feb-April 2023](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/62): > > @jondkinney @Tim_Kim @YvetteLans @Tommy_Hedley Not much to show about tables, we are still migrating to AG Grid and even MVP is at least a month aheadā€¦ [2023-05-02 09.54.44] ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [May 15, 2023, 9:59am UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/67 "2023-05-15T09:59:51Z")
We are curious about the scope of the table improvements because we run into the following. At this moment we donā€™t have a good way to plan tasks in all different projects. Because the planning of those tasks depends on the total workload of all (internal + client) projects. We would like to have one overview with: - all active projects - and all tasks and subtasks within those projects So that we can determine the deadline or planning for each task/subtask. Because subtasks are currently a self relation of tasks, we canā€™t show them in one overview (because this can currently only be achieved when tasks are the highest level ā†’ in this case project is the highest level) Will this be possible once the table improvements have been implemented? So the desired situation is: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3952f96f88a7a65ee2fc719c6dc94110faac0bae.png) We have postponed the go-live for our customers. - Because we are delayed due to personal circumstances - But also because we are waiting for the table improvements ā†’ this has a huge impact on the construction of our workspace If possible, we would like to know the scope of the table improvements in [the roadmap](https://the.fibery.io/@public/Public_Roadmap/Roadmap-Board-5974) so that we know better what to expect from those changes. ---
**Author:** ![mbs](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mbs/32/4064_2.png) [@mbs](https://community.fibery.io/u/mbs)\ **Post date:** [May 15, 2023, 11:56am UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/68 "2023-05-15T11:56:11Z")
Sorry to butt in, but can you not have that exact view with Lists? Project \> Task \> Subtask levels with filters on ā€œActiveā€ and whatever else you only need to appear, should have the desired result. Or is there a particular reason that it has to be tables? ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [May 15, 2023, 12:06pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/69 "2023-05-15T12:06:09Z")
List view is also fine šŸ˜„ But unfortunately thatā€™s also not possible atm. Self relations only show when they are the top level in hierarchy (so task / subtask). Not when the first level in the hierarchy is ā€˜Projectā€™ or ā€˜Featureā€™ for exampleā€¦ And when you want to add more information, then tables are more user friendly than lists. Thatā€™s why I asked it regarding to the coming table improvements. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [May 15, 2023, 1:45pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/70 "2023-05-15T13:45:09Z")
This is frequent request, but it is not related to tables. I will ask devs what we can do here for Lists ---
**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\ **Post date:** [May 15, 2023, 4:40pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/71 "2023-05-15T16:40:18Z")
Thanks! Since the new table grid looks like an all in one table/list I was hoping that it would be fixed via table view šŸ˜… Especially when you are coming from ClickUp itā€™s a pain in the ass when subtasks are not showing in views. We use them a lot in our set-up. ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [May 15, 2023, 4:41pm UTC](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940/72 "2023-05-15T16:41:38Z")
Sure, when it will be done in List, it will be done in new Table View (since it is based on List implementation), but in List you will have it faster [Previous page](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940.md?page=2) [Next page](https://community.fibery.io/t/fibery-roadmap-for-feb-april-2023/3940.md?page=4)