My Kanban board is completely empty

Hello Taiga team. This morning I was working on my Kanban board, moving some stories to the done column, and suddenly the board appeared completely empty, as if it had never existed.

I have several other projects where my Kanban board is still working, but this is the only project that is really active, so it is particularly problematic.

Could this be the result of a technical issue or the new pricing model?

Hi there,

That has nothing to do with the new pricing model, but it could be a technical issue or javascript being blocked or something similar.

Are you using https://tree.taiga.io or a custom instance? Have you tried doing a hard refresh? On Windows/Linux it would be Ctrl+Shift+R.

Best!

Hello Charlie,

I am using tree.taiga.io. I tried a hard refresh but nothing changed. I just try to disable/enable kanban from the module’s setting page, but kanban is still empty…

Hi again,

Please write to support@taiga.io with your project slug and your user email, and we will take a deeper look.

Best!

Hi. It happens the same to me.

Hello! I had the same problem and I was using Safari. When I logged into my account on Google Chrome, everything went back to normal :smiley:

Hi. I haven’t written to technical support yet, but I just want to add some extra information. After hard refreshing on Chrome, I went to Safari and I found my kanban there, but it disappeared when I started interacting with it. The same happens with other navigators. I used Opera to find my kanban and I interacted with the Kanban board that makes it disappear. I finally opened Firefox and I decided to not interact anymore with the board in order to copy everything in another board.

Also I tried to export/reimport the project but it doesn’t exports the stories, so I cannot really find a solution there.

Hi there,

Have you tried private navigation to discard issues with extensions?

Regarding exports, they do include user stories and anything needed to recreate a project.

Best regards.

1 Like

Hello Charlie, thanks for being here ! I confirm that private navigation is bringing back the Kanban board in all navigators ! So I uninstalled all extensions, made a hard reset but… the Kanban board is still missing in the main navigation window (tested on Chrome and Safari).

G

Hi,

It looks like this is due to a faulty default saved filter that includes an epic=null that return 500 when filtering on user stories.

This happens when you remove all filters (apprently thos on epics), and this is somehow saved in local storage and is persistent accross logout/logins

Work around the issue:

  • Avoid using ā€œnot in an epicā€ filter (creating the epic=null faulty param)
  • Clear local browser cache (F12/Application Tab/Storage/Local Storage in Chrome) , you can clear all here

Permenent fix : i guess fix these URLs returning 500 (epic=null is the trigger):

/api/v1/userstories?epic=null&project=2&status__is_archived=false

/api/v1/userstories/filters_data?epic=null&project=2

Hi Romain,

I definitely tend to use filters in my kanban, so you are probably pointing to the heart of the problem.

We discovered before that using a private window in any navigator can brings back the kanban model. But when this kanban appears, there is any visible filter applied. That makes impossible to erase any filter.

Also I have to add that : after opening the filters, in order to verify if I can change something there, if I quit the Kanban board, then it is not anymore available and I cannot come back to it. So defintley the opening filters action is triggering the issue.

Hi,

Well maybe the symptoms i described were not that correct. It looks like it’s using the ā€œnot in an epicā€ filter (activate it or remove it later) will let a ā€œdefaultā€ filtering on your local browser persistent and blocking the page to load correctly. This is not attached to the profile, only local browser storage that sort of ā€œcomplementā€ the profile paramters get after login.

Tath’s why it’s ā€œworkingā€ with a private navigation, but persistent accross logins when triggered.

I’m pretty new with this product so i do not know the formal way to raise the bug/issue. but that’s the root cause, having the API misreacting when having a ā€œepic=nullā€ filter on some of its endpoints and making the frontend failed to fully load (including the filter buttons that could have helped to modify these filters)