This was found on http://ecosystem.atlassian.net by jgordinier.

It is reported that certain issues, which were raised with Bonfire, are not appearing on the SF Ecosystem Rapid Board.

An example of such an issue is UPM-2285. It appears in the search results when viewing the filter backing the board in Issue Navigator, but it does not appear on the board.

I have checked the following common causes:

• Status mapping - is Open status
• Sprint and Rank field configurations - all normal
• Empty Sprint field
• No active filters

What's interesting is that, when viewing the issue from View Issue page, if I choose the 'Go To Agile Board' operation, it attempts to go to the board, only to not find the issue (select it) once it gets there. Normally, when an issue does not appear on a board, the operation will fail.

Another interesting fact is that, once the issue is Ranked To Top/Bottom from View Issue page, it suddenly appears on the board. So you would think that it might be an indexing issue. But if I do a simple edit of the issue's description, this does not solve the problem. So it could be a problem with the rank index.

I do not have access to the logs to check what's going on – this will be my next port of call.

Workaround

Bump the Query Result Limit on ecosystem.atlassian.net. You can safely bump it to 1500-2000; I imagine setting it to ~5000 wouldn't cause too much havoc;

Refine your board filter (or create a new board) to reduce the number of issues that appear in your backlog. One could argue that having ~5,000 issues in a backlog is not very manageable.