I have a board that combines several task databases from different spaces into one “all tasks” view. On that view I set up filters and a few color coding rules, and they apply across all the databases at once. I set them up one time in the All Databases tab and they work for everything. So far so good.
The problem starts when I add another database to the same view. The moment I add it, the filters that were shared across all databases get broken out into a separate copy for each database. The color coding rules do the same thing. So instead of one filter that applies to all databases, every database now has its own copy, and the All Databases tab stops showing a single shared filter. It says it can’t display filters from different databases together.
I didn’t expect that. I expected the filters and color rules I already had to just keep applying to all the databases, the new one included, the same way they did before I added it.
So my question is, is this how it’s supposed to work? Is there a way to add a database to a view that already has filters and colors set up, without them getting split apart per database? Right now adding a single database forces me to set everything up again for each database, or rebuild the view from scratch.
One more thing I noticed: after this happens, the pinned quick filters at the top also stop merging and show up repeated for each database.
Yeah, this is expected behavior. The annoying part is that you can’t have some filters be for all, and other that database specific. Its either all together or all separate.
In your case it seems like all of them have the same filters, so they can be all together. The way to ensure they get merged together is if:
The field names being filtered are the same
The field types being filtered are the same
The filter values are the same.
(maybe the order of the filters? I am not sure about this one though)
This will make it go back to global instead of split across databases. Have a shot and let me know if it works. Then you can edit the filters globally instead of one by one.
It would be nice if a newly added databases adds the global filters automatically if it contains the same field names and field types. But the reason this happens now is that a newly added database does not get any filters by default, so since it is different from the other databases, all filters get split per database.
In my case the fields and types are basically the same across the databases, but a newly added one still does not pick up the existing global filters. It comes in empty, so everything splits, and I have to rebuild every filter on the new database by hand to get back to global. With the complex nested filters and color coding I have, that is a lot of manual work and easy to get slightly wrong.
What would really help is a newly added database just inheriting the existing global filters when its fields match, or being able to save a global filter set as a template and reuse it. Even better if it could be set through the API so an agent could handle it. Having to rebuild everything by hand for one new database feels off.
