Thread View is a View that shows Comments from a single Entity. This is as close to Chat as we can get . For example, it can show comments from specific Feature, or Account, or Channel. Just remember that every message in Thread View is a Comment, and you may invent some specific use cases.
Thread View is an early experiment to explore how Fibery can enhance communications and replace chats in some use cases. Navigate to Settings → Experimental Lab and enable Thread Views. There is absolutely no guarantee we will keep this feature in production and improve it. We will collect your feedback and decide.
Here is the video that shows Thread View in action for our team daily updates.
Grid View is quite close to official release and full Table View replacement. We still have ~20 bugs to fix and small improvements to add, but it seems in two weeks we will release it and replace the current Table View.
Here are some fresh improvements:
You can embed Grid View into rich text field and documents now
Copy/Paste content in Grid View works now
Rows in grid stays selected on unfocus
Add and Edit Fields in popover always
For a consistent UX, we always create and edit Fields using a popover. Popover has a decent width that we control, doesn’t prevent user from scrolling, neither vertically nor horizontally, so Creator is free to explore the surroundings.
What happens with the fiery volcanoes across the globe
What happens with the FIBERY GRID???
I beseech you: tell me of the future.
Minh_Tri_Do_Hang has already shared with me that he, too, is from the future, and that in his future, the grid just works. That grid. Your grid. It just works.
From the lowest of lows to the highest of highs, his grid just works.
Tell me Alex, what have I done such that you would smite me like this.
I am but a poor man. I simply seek the truth. I long for the grid that works for us all.
One day, that grid shall reign supreme and in its incandescent golden light we shall all shine together. Don’t hate me because I’m a poor cobbler; together, we shall all, whether rich or poor, kings or cobblers, revel in the glory that is the grid.
Don’t take the grid. You may seek to keep that grid from all of us, but that grid is eternity, that grid is life! You can take my life, you can take my dignity, but you will never take my Gggggggggrrrrriiiiiiiiiidddddddddddddddd.
not really smooth as current table view
I just tested it yesterday, it was overlap the 1st entity when I tried to paste mass note from google keep to grid view and I lost several entities last night
But i think it’s good to know that, it can be completed in next 2 weeks, really appreciate the effort of all teams to try to pleasure all requests
Just tried it briefly to see how we could replace Slack in some instances.
Our use case
As a digital agency, we work with a lot of clients. In Slack, we have a separate channel for each client. We try to do as much as possible in Fibery and keep broader discussions in Slack.
If we would have the broader discussions in Fibery instead, we would like to have a context-filtered view in a Smart Folder for each Client. This would sit along other views that collect Projects/Tasks/Meetings/Reports that are Client-specific at the moment.
I’ve actually added a Comments field to the Client entity expecting it to show up in the Thread view within a Client Smart Folder. This way, we would only have to add a view to a Client Smart Folder, add Comments to the Client entity and have Threads automatically for each Client (one can dream at least :))
Overall I say it looks promising for our needs! It would be very nice if we could keep everything documented/discussed in Fibery to get away from context-switching between Slack/Fibery.
It would be nice to have the Threads view automatically pickup the entity in a Smart Folder
It would be nice if the pinned Threads view was filterable (I see you’ve already mentioned this in the user guide)
p.s. I think it would be very difficult to replace Slack for us in its entirety since a lot of our clients have “schelling pointed” towards it. But it would still add a lot of value even if it didn’t replace it completely (or had the ambition to).
Again a great update to an already great product. Threads are amazing and adoption will be high I guess… Only thing that would keep me from using it more is the lack of a mobile app or easy integration.
I am not sitting at my computer all day as I am a lot hopping from meetings and events. So having a way to easily communicate is key. I use slack and beeper mainly. But I would love to get rid of slack as the User-Interface is something that really is not my favorite and the added cost is also something that we would like to reduce.
What are the plans about that ordo you have workarounds to make the mobile chat experience better (in future updates)
Threads: how are you implementing DMs into this system, when you voted slack completely out? Adding a comments section to the user would be my first idea - but all of that conversations then would be visible to all, correct?
We didn’t move all comms to Fibery. We just moved our practice of posting daily updates (which everyone gets to see).
So indeed, direct messaging (i.e. private communication) is not supported with the current threads capability
I really love the Threads and it opens plenty of use-cases I think.
Just a question regarding the Threads notification folder in the upper left: what are the Thread views it will contain for each user? All the views from all the spaces? Only the views created by the user plus the ones he participated in? What about thread views created in the Personal space, how does it work?
Love this feature! Will definitely test this internally.
It would just be very nice if the thread replies wouldn’t open in a new window, but the same way as the regular comments, with an uncollapse. Like this:
Also I wouldn’t call it threads, but channels instead. For instance hierarchically speaking Slack would be: Channels > Thread > Reply. Now you are making it: Threads > Thread > Reply.
Also I had some difficulty even creating a threads, because I would expect a simple “add thread” button, which there is:
But then I have to link it not to a space, not to a database, not to a view, but to an entity. Which was a bit difficult to figure out, not very intuitive. Wouldn’t it be much simpler if it’s just “add thread” button, I click, and it’s there linked to the space? Or not even linked, just free floating, not linked to any space, just a separate thing altogether that lives (sorta like a view) within a space.
I’ve discovered an interesting way to work with Threads. When brainstorming is contained within a task(entity), establishing a ‘Thread’ can help organize the discussion efficiently. This approach enhances focus for the following reasons:
If notes within the ‘Thread’ are not converted into tasks, sprints, or projects, they will disappear. This is because the task has a deadline that must not be postponed.
Discussing matters in regular ‘perpetual’ chats often leads to the temptation to defer decision-making.
As a result, we create a chat with a finite lifespan.
+1 to focus.
On the other hand, a ‘Thread’ alleviates the psychological pressure often referred to as ‘needing to distribute all ideas in the chat.’ This is because ideas that are not acted upon are discarded due to the task’s deadline, which cannot be extended to tomorrow.
+1 to mental clarity.
Such a psychological trick improves productivity in brainstorming sessions and overall task focus.
The key is to embrace the idea that the deadlines for such tasks are immovable.
Would be also awesome if we can see next to ‘Threads’ the total amount of open messages. Currently you’ll only see this while expanding the threads. But since that can take a lot of space we often collapse the ‘thread menu’.