But I am excited for everything else Keep up the good work!
But I am excited for everything else Keep up the good work!
This really made my day We are currently struggling with permissions, tables and comments/notifications. Creating all kind of (pretty ugly) workarounds so really glad that this is in scope for the coming months
And pretty sick to see what has been improved in the last months. Those new functionalities were a real game changer for our setup
This is also awesome! In the meantime I’ve created a workaround for a clean left menu which is working pretty well. Maybe we can inspire people with it
Previously our CRM space looked liked this for a user (and then imagine in total 8 big spaces like this )
In our new set-up we’ve hidden all those databases and views for users and made our own menu.
It is really cool that with all the functionalities today (and some imagination + help from support) we can build the most awesome solutions
Note: unfortunately there is no room for smart folders anymore in my setup, but it’s a pretty perfect in between solution for non tech savvy users.
You can create smart folders + views in hidden databases and link those views in documents. But the problem is that it’s currently not possible to filter out entities like in a normal smart folder. And therefor if the system asks for which entity the view is, user will see all kind of entities that are not applicable for the situation. Which causes brain melt for my clients
Because the mention of Whiteboard I would love the ability to use Mermaid either in documents or both documents and whiteboards.
Especially with the great implementation of chatGPT into fibery, the ability to have it generate diagrams and workflows right into fibery would be awesome.
That’s great news and massive thanks to the whole team working on releasing improvements regularly and tirelessly❣️
Besides the FRQs filed and that I’ll keep filing, our take on the plans for the next 2 quarters:
Again, thanks for all the hard work you all are putting into this. Hope you don’t mind our candid feedback.
Great news with a few things on this list in particular:
These are huge features, in particular being able to resolve comments so they can act as sort of “lite” tasks. If you could guys could be sure to include that there is a follow-on comment explaining what the resolution is, you have a really differentiating feature here! Otherwise you just mark “resolved” but somebody reading that might not know what happened to resolve the comment…I wrote some more details on how this could look here
I also want to mention just to make sure it’s on your guys’ radar how good it would be to have a sort of activity feed on entities if you could Have references and comments with the option to show chronologically as they are added. It has become basically our top Fibery SOP in my team for members to scan BOTH comments and references to see the latest on an entity. At times we have the latest comment say 3 months ago, but the entity was referenced (and by association updated) many times earlier. Example: Closing the last task in a project - when that task is closed, I comment "I’m also closing out this project…"which I tag in the same comment, and voila I can update both in one, quick fell swoop. This saves me from having to go over and comment in the project’s entity that I closed it. Also, it gives context to the reader that the project got closed at the same time as when the last task was closed. There are so many uses of this ability to tag/reference multiple entities at once around Fibery, and having the comments/references stream sort chronologically would really help the foundation of using this method.
Well, we are focusing on product teams and product companies, and don’t want to compete with Asana and Trello, for example. We want to cover use cases that are demanded by product teams and these use cases are one of those. Note that we are not going to slap features, but improve the platform. For example, if you will be able to work with References in a better way, it can be applied to many other knowledge capturing cases, not only feedback management. Fibery as a platform is relatively OK, but we also need to enable quite concrete use cases to grow faster.
Looking forward to the new Table release. Any details on what additional features we might see in the future? Hope to see the capability to have calculation row (sum, mean etc) and freeze row/column. And overall faster keyboard navigation will be great.
Wow, this is amazing news. Really happy with this roadmap.
Not sure if the Fibery team has evaluated Weje (A free online web whiteboard for visual collaboration inside) but it has some interesting features.
Thanks for elaborating, @mdubakov. Glad to hear that you see that whatever will be done with References will work better across the product. I’m excited to see how that empowers the general use.
Guess what I wanted to bring across is that for our product team, I do currently not see this as that crucial. I might be missing visibility tho.
I just hope that the Whiteboard gets the love it needs. To us, that’s one of the biggest selling points and currently sadly just workable…
Hope to see the capability to have calculation row (sum, mean etc) and freeze row/column. And overall faster keyboard navigation will be great.
In the first release we will mostly have the same feature set, with some additions
Then we will add more features, like totals for columns, etc. We will not stop till Table View will be powerful enough and usable enough.
Since you are working on the emojis, I would like to give some feedback.
In a couple of databases we are using single select fields as a workaround for state.
Due to the possibilities we have with the normal state field (like state = final in formula’s) we would like to change those single selects into a traditional workflow field. But we don’t like the looks of it.
See these 2 examples:
Wonder if you guys agree with this.
Could you tell me please how emojis were added to single-select? Were they selected with our icon/color picker or were they inserted using native OS emoji picker as a part of title?
To me it looks like you inserted native emojis to single-selects but for Workflow field you selected them with our picker. As a part of emoji-color-picker-unification we’ve decided to use Twemoji (twitter emoji) for all non-apple users in our pickers
So, as a workaround you can still insert native emoji to workflow field as a part of text but in that case your colleagues sitting on Linux or Android will see emoji in their OS style (e.g ✅ White Heavy Check Mark Emoji)
Whilst we’re talking emojis, some way to convert icons to text in formulas would be useful.
eg. I have a multi-select that sometimes gets a bit hectic. The ability to just string together the emoji icons so views with less space can get a shorthand would be handy, and the thing that’s stopping me is that emoji icons can’t be inserted into text, even if the emojis themselves are allowed.
The emojis in the single-select were added via the default option from Microsoft as part of a the title. And you’re also correct that we used the emoji picker for the workflow field.
So yes, we can replace the emojis in the workflow field with our own emojis provided by Microsoft. But unfortunatelly, we still dislike the way it looks. I had the hope that choosing an emoji would replace the dark circle. Now we basicly have 2 emojis
See the image below were we have changed the emoji into our own (as an inline text emoji).
Just out of curiosity, if I have a CRM that I share with partners companies, will there be a way that I can add child notes to a company/person without being accessible to the other partners companies? (child relation)
Seconded. I have 2 applications that would be instantly done if I could use ChatGPT to make diagrams. But the issue I’m having with DateTime is about 3 hours away from making me give up on Fibery entirely – and I could just port Mermaid to something from my own server if I go back to hacking Google Sheets and Zenkit together.
This is a great roadmap, thank you! Drop down entities in tables and improved comments will be game changing.
Sure, this is the goal of entity-level permissions. You can isolate child nodes by a parent node by giving or not giving access to a parent node. So in your case you will give access to Company A and only notes linked to Company A will be visible to a person.
Great news re ag grid - solid product. Looking forward to seeing this implementation.