Kanban board is empty

[Devin Canterberry]

TL;DR. Anyone know why a Kanban board would silently fail to load issues that match its associated Filter Query?

For some reason, my Kanban board is empty, despite its Filter Query matching lots of issues and being shared with all project roles. There are no errors in the browser console and all network requests after a hard page refresh are coming back with OK status. Other members of the project are also having the issue.

I've tried updating the Filter Query to be a simple `project` match, to no avail.

This is an Atlassian-hosted JIRA instance, so we have not (and cannot) make low-level changes or access the underlying database.

[Luciano Fagundes]

John

As a best practice we recommend to use the database native backup tools. Per our documentation "When JIRA is in use, XML backups are not guaranteed to be consistent as the database may be updated during the backup process. JIRA does not report any warnings or error messages when an XML backup is generated with inconsistencies and such XML backups will fail during the restore process. Native database backup tools offer a much more consistent and reliable means of storing (and restoring) data while JIRA is active".

Cheers

Luciano Fagundes

[Nic Brough -Adaptavist-]

1. For small Jiras, it's ok to use the automatic backup to xml, but as you say, you can't exactly schedule it neatly.

You would be far better off moving to the recommended backup method - use your database's standard tools to take a backup of the database. You'll be able to schedule those for when you want them.

2. What's the reasoning behind backing up every 10 minutes? That's far too frequent for internal backups, you're stressing your server for no benefits. Most people backup nightly, or sometimes half-daily (but if they're that concerned about data loss, they quickly move to database backups)

[John Zhang]

Thanks for your reply. But I want to know why jira can't backup every 10 minutes(or more time) via the setting, this is the critical issue. 10 minutes is only for test.

[Nic Brough -Adaptavist-]

Because it hasn't been written that way. The basic backup service simply reuses the "repeat on a loop" scheduling that was built for other services. You can trigger a backup by hand as well, but there's no need for anything more advanced because if you genuinely need something more clever, you really should be using the database tools as I recommended before (see https://confluence.atlassian.com/display/JIRA/Backing+Up+Data)

[Pedro Souza]

Hello John,

Please, see our official documentation for Automating JIRA Backups, I believe it will help you:

https://confluence.atlassian.com/display/JIRA/Automating+JIRA+Backups

Cheers.