So I’ve been using Fibery threads and they’re very nice. They could definitely take the place of slack because they can be so enmeshed in the workflow.
It would be great if you could attach a few entities to a thread, even if it were a manual process.
Here’s a use case. Recently we’ve gone through a big, unpleasant bookkeeping transition. There are around 5-8 important entities in multiple space and with different people. I would love to see:
#bookkeeping
… That had comments from each of those documents in one place. Of course that’s more challenging because it’s like separate threads within a thread, but that overall concept would be a godsend througout Fibery, for me.
While this does seem like an unusual way to make a “Channel” it also seems potentially quite powerful. I wonder if there is some version of this that would work intuitively and for enough uses to make it worth implementing. For example sort of Thread View that works like Smart Folders, e.g. setup rules that then include all Comments from those Entities. Within the view I suppose you’d want to have them represented as “sub-threads” for clarity… Anyway, an interesting idea.
The idea indeed is interesting. Technically it can be done, but I’d like to explore use cases.
(Note that were are not focusing on Threads improvements in the next few months though). The value is not super clear so far…
There are around 5-8 important entities in multiple space and with different people.
You may Watch all these entities and receive notifications about all comments, so it is unclear how Thread View will be better.
If comments become entities, then creating views to aggregate and filter them across different meetings becomes very easy. I think that is the way to go.
In the meantime, a more complex solution can help to aggregate scattered discussions around a particular topic using the following setup:
In order to pull comments from multiple entities, it is not difficult to adapt the script to fetch all comments from all entities of a particular database and perform the same operations, like filtering for a tag or entity mention.
I may create such script in the future, but I rather see that the Fibery team makes comments entities that can be displayed and filtered in views just like any other entity, keeping the ‘threading’ functionality.
I actually suggest the following: that the Fibery team looks into a generic feature that allows ANY entity to be displayed in a thread view, not only comments.
We’re importing HubSpot deals into our Fibery workspace & tracking them through their entire lifecycle. A single deal could spawn projects, tasks, follow-up deals, and sub-projects. We track status updates in comments, so I’d love to be able to show a single thread view of all comments across all of these entities.
Ideally, I’d be able to set this up as a mirrored view in a smart folder of open Deals.
Big +1 for this feature, or alternatively allow Threads to contain other Threads
Here’s my usecase:
We have a marketplace where there are Buyers and Sellers who operate within a physical Market (city) and transact Products
These Products are actually very complex objects in and of themselves and often warrant discussion (i.e. Threads) on their statuses. However, our employees’ scope of work is defined as either a Market, a Buyer, or a Seller. The employee responsible for Buyer A wants to observe their world through a thread that is Seller A + ChildProducts(Seller A). The employee responsible for Market X wants to observe their world through a thread that is Market A + ChildBuyers(MarketA) + ChildSellers(MarketA), which would in turn also include ChildProducts(Seller A)
Without nesting, we either have a massive proliferation of Threads that’s impossible to reason about and see notifications on, or we need to discuss at “higher level” threads which degrades their context-specificity (e.g. discuss all Seller A’s products in the Seller A channel) and actually cannot work in many scenarios (e.g. in the middle of a transaction, Seller A’s product is linked to both Seller A and a Buyer C).
So we also want multi-parenting. A different employee’s area of responsibility might be Products with Type=Mechanical. They want all the activity from all those specific Products, while that activity is also aggregated up its Buyer → Market chain.
EDIT:
Another way to do this (and what I’ve tried hacking together with automations/API) is an auto-crossposting feature that would navigate our conceptual hierarchy (products/buyers/markets) to post references in the correct places. It’s pretty messy and the biggest problem is the final rendering is bad/confusing. This approach would be nice if Threads had a nicer “Mentioned Comment” rendering than it does currently (i.e. right now it just renders the name of the Thread, but it should render a preview of the comment itself) – this would probably be more like an “Embed View” of the comment rather than the Mention feature.