I cannot seem to find out how to do this if it is even possible: If I have a bunch of requests come into a tasks board, and I want to “bulk edit” them, can I do it? Like, set due date on all or, set priority to high on all etc.
There are a lot of aspects of Fibery which are “frictionless” which is fantastic, but I’m hoping I am missing something.
This makes Fibery unusable for a lot of usecase, because it means we can’t really add new columns on existing tables and quickly set a value to all cards
=> we would have to do them one by one, and there can be hundreds of them… which is not understandable, I am maybe missing something too for doing this?
I can’t see any way to do it in table or board views for instance,
There is also the ability to see Rich Text fields in the Table view, which is hindering a good understanding of the tool and no-brainer imports, but there is the workaround of using only simple text fields will do the job, so it’s clearly 10x less critical than bulk edit
We are using Fibery similar to what is displayed here: https://www.youtube.com/watch?v=g7I-m3Bzzvg and bulk transitioning/editing items from column to another column is a must. When you plan for iteration, there are lots of moving issues around and it’s really tedious to do one-by-one.
I would also like to support this request. In addition, per @hannukle your comment, one other bulk action I’m really finding myself needing is being able to move an Entity to a different type - for example if something went in Fibery as a task, but it’s really a Project.
I talked about that here:
If you think about the structure of Fibery, and one of the things that makes it great, it’s that Entities are each a “type” of their own. In most other work management apps, you’ll have a notion of a “task” entity. Then, if you want to use the task as a “customer,” or “asset” like piece of equipment or blog post, you have to “tag” that task to give that attribute. In Fibery, you can just create a “type” right off and build it out as your need requires. That’s great.
However, I really think you need to be able to change the Type as during the flow of using Fibery at scale, this need can happen a lot. In the other Work Management apps that use “tasks,” you can easily just swap out tags at will. But in Fibery, without being able to change “Type,” I am finding a pretty big restriction in daily operations without having this capability.
Just to add another case to this, I have seen the need to batch relate more and more as my team moves in Fibery. This happens when periodically somebody on the team (I am onboarding more and more) bulk creates a list of Entities out Rich Text Bullets. But the Entities didn’t belong in that relation. So I’ll need to “re-relate” a group of 8 - 10 entities, which is time consuming.
For purposes of comparison, Notion has a batch capability and relating is one of the things you can do with it.
but it would be better to have that directly in Fibery, especially when adding to a “many to …” relationship where you already have other entities.
Example: I have a Contact type (representing people) and Event type (conference, webinar, etc). I have a many to many relationship called “Attendees” between the 2 types that represent who attended the event.
I would like so select in the Contact Table view several Contacts and add a new event to the Attendees field. I should have the possibility to indicate if I want to replace the existing values or just append the new Event to the existing Events (default case for 99% of uses cases I think).
I see 2 solutions to do that:
batch edit in a View (Table seems more convenient from UX standpoint and enough for me, but in theory could be done in other views as well)
batch action button with variables asked at execution: once the Contacts selected, I could click on a batch Action Button that would open a small overlay form to input the variable. In my case I would have create a “Add event as Attendees” button, as seen in the screenshot, but with the value empty (or indication that this is a variable to be set at runtime) instead of “Cleantech Forum Asia 2019”