Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to search in large databases

Alberto Yánez Montesdoca
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 1, 2026

Currently I have a database with 500+ entries. In kanban view the search does not bring up matching cards. In table view I have to load the full database (by scrolling to the bottom) and then search does work.

 

Is there a solution for this? 

 

Thanks

2 answers

0 votes
Monika Ambrozowicz_Seibert_
Atlassian Partner
June 4, 2026

Hi @Alberto Yánez Montesdoca!  As @marc -Collabello--Phase Locked- mentioned, Confluence databases are not particularly user-friendly, and the behavior you're running into is a known limitation. The kanban and table views don't perform a server-side search across all records - they work against whatever's been loaded client-side, so with 500+ entries you're stuck either scrolling the full table into memory first or getting incomplete search results in kanban. There's no native workaround for this within Databases itself. 

 

If you're open to install a marketplace app, I have a solution to this limitation - the app that's called Properties. Full disclosure: I am affiliated with the team behind the app, but I genuinely believe is it the best solution for you. 

There most significant difference between Properties and Confluence databases is that instead of a standalone database table, in Properties each record lives as its own Confluence page with structured metadata attached (typed fields like drop-downs, date pickers, user pickers, statuses). You then build a Property Report that aggregates those pages into a filterable, sortable table view, or a board view for the kanban-style visualization. Because the data lives in indexed Confluence pages, search works reliably without needing to pre-load everything. You can also filter and sort the report directly without depending on the browser having loaded all records first. 

 

properties-table-board.png 

In the screenshot above you can see an example of a simple content planning report I built with Properties - first a table view, and then the kanban view. 

 

Happy to clarify how the report filtering works if you want to dig into a specific use case before committing to a change. 

 

 

0 votes
marc -Collabello--Phase Locked-
Community Champion
June 1, 2026

Unfortunately the ergonomics of databases are not good ....

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events