Csaba Vertessy added a comment - 21/Jan/2015 3:42 PM Hi Michael Tokar: and what about the related issue? Can you give us some feedback please? Thank you!

Michael Tokar added a comment - 27/Nov/2014 2:33 AM I am resolving this issue as a duplicate of the linked one. Please follow that issue for updates. Regards, JIRA Agile team

intersol_old added a comment - 17/Sep/2014 5:02 PM What is not specified here is that the core problem is that the board filter must include all the historical issues in order to be able to generate the reports properly. If you put only the unresolved issues in it, the performance problem is solved with planning, but reports are damaged, Also the WORK tab would be affected because dragging issues into last column (done) would make them disappear. The issue is presented in more details here https://answers.atlassian.com/questions/8620924/how-to-make-agile-board-planning-loading-to-a-decent-performance-level – be sure you read all comments. My impression is that the correct solution for this is to add two automatic filters: for PLAN mode, do add "Resolution = Empty" to the filter query (so the tons of issue would not reach the client) for WORK mode to add Sprint = xxx (or something similar), so it would also be really fast. for REPORT mode, to do nothing yet, as this one really needs tons of issues to do reporting on. Still it would be wise to test the performance with a 10-20k issue filter. People didn't report speed issues with reporting, or at least not yet.