Active sprints: Failed to execute search

[ionut_lenghel]

Does anybody know why do we get this error? Nobody in the company can open active sprints.

[Ramadhina Dewi]

Hi @ionut_lenghel 

We experienced the same issue just by this morning. Several projects in the company were affected and we couldn't access the active sprints. But we decided to done a quick fix by re-created scrum/kanban board for each of the affected projects and use the new one as the default board instead (we also deleted the old error board). I know this might be bothering and may take some time, yet still better than cannot accessing the active sprints at all.

Hope it helps!

[Felix Kenton]

We've suddenly started having the same issue this morning with a Kanban board, and it is not the result of any configuration changes. The board was fine yesterday evening and then broken at the start of the working day today, and the Audit Log has no activity in the past 7 days.

[Veera]

@ionut_lenghel 

It could be something to do with invalid issue type or one of the custom field configurations.

Reach out to support by submitting a ticket with the board details in the Support portal. Support team should be able to help you identify what might be causing the issue.

[Ste Wright]

Hi @ionut_lenghel, @Felix Kenton 

It's worth checking the audit logs to see what the issue might be.

I've seen this issue before when a filter is not valid - for example:

• The board filter has a project in it which doesn't exist or..
• A quick filter doesn't correspond with a filter (eg. a quick filter references issues which are exempted in the board filter)

If all the boards aren't working though - rather than just one - the audit log is more likely to have the details. You can also try performing a re-index of your instance.

Ste