Confluence Database filter view without saving?

[Maja Vallin]

Hi,

I have a case where a lot of people will be using a Confluence Database and all of these users of course would like to filter their own view.

With the new changes to Confluence Database the user will always get the option to "save view" TWICE, and if the do that they will most like f*** things up for the other users.

Previously you had to go to the top banner to save a view and temporarily changes was not saved unless you actively chose to change them.

Has anyone found another way to solve this without having to create a own view for each user?

Xoxo Confluence Girl

[Mia Tamm]

Hi @Maja Vallin ,

Yes, this change has been frustrating for many of us! Right now, Confluence Databases don’t support “personal” or temporary views — any filter you apply triggers the “save or discard” prompt for everyone.

One workaround we’ve tried is to instruct users to always hit “Close without saving” after filtering, but as you said, it’s risky and not very user-proof.

A more controlled option (though not ideal) is to duplicate the database on a hidden page, create preset views for different teams or roles, and let them filter there without affecting the main one. But sadly, there’s no native way to isolate filters per user yet 😕

If Atlassian adds per-user views (like in Jira dashboards), that would be the real fix.

— Mia Tamm from Simpleasyty